You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by GitBox <gi...@apache.org> on 2022/04/22 03:07:11 UTC

[GitHub] [cloudstack] CKrieger2020 opened a new issue, #6298: Place VM's on the same network as the CloudStack-management server

CKrieger2020 opened a new issue, #6298:
URL: https://github.com/apache/cloudstack/issues/6298

   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and main branch are affected too.
   Always add information AFTER of these HTML comments, but no need to delete the comments.
   -->
   
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
    * Other
   
   ##### COMPONENT NAME
   <!--
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   -->
   UI, IP
   
   ##### CLOUDSTACK VERSION
   <!--
   -->
   4.16.0.0
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   I am trying to find a method of placing newly deployed VM's on the same network as my management server, but so far it only allows me to create guest VM's behind a NAT with a private IP address. I need to create multiple VM's hosting services that can be routed to an external DNS. My concern is that the NAT will make routing to these machines impossible.
   
   I have tried changing the network offering on my guest network from "offering for isolated network with NAT service enabled" to "offering for isolated network with no NAT service enabled", but it gives me this error:
   
   "can't upgrade from network offering edad787d-baa0-4ca8-a67b-bd288adc6d37 to 052cee24-272b-44f1-a4df-4b5da7a30744; check logs for more information"
   
   I would choose this during network deployment, but I do not have the option to choose "offering for isolated network with no NAT service enabled" until after deployment. 
   
   I would appreciate any advice you can give to help guide me from here as I am new to cloudstack
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   Place all deployed VM's on same IP range as the management console itself. 
   
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   Forced to deploy VM's behind NAT per default configuration
   <!-- Paste verbatim command output between quotes below -->
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [cloudstack] boring-cyborg[bot] commented on issue #6298: Place VM's on the same network as the CloudStack-management server

Posted by GitBox <gi...@apache.org>.
boring-cyborg[bot] commented on issue #6298:
URL: https://github.com/apache/cloudstack/issues/6298#issuecomment-1105956643

   Thanks for opening your first issue here! Be sure to follow the issue template!
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [cloudstack] rohityadavcloud commented on issue #6298: Place VM's on the same network as the CloudStack-management server

Posted by GitBox <gi...@apache.org>.
rohityadavcloud commented on issue #6298:
URL: https://github.com/apache/cloudstack/issues/6298#issuecomment-1217984828

   @CKrieger2020 can you check the above suggestion and re-open the issue to discuss more.
   To discuss further questions, you can raise them on the users@ and/or dev@ ML https://cloudstack.apache.org/mailing-lists.html
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [cloudstack] DaanHoogland commented on issue #6298: Place VM's on the same network as the CloudStack-management server

Posted by GitBox <gi...@apache.org>.
DaanHoogland commented on issue #6298:
URL: https://github.com/apache/cloudstack/issues/6298#issuecomment-1127332650

   @CKrieger2020 this is certainly a new use case. After a quick read I think you might want to investigate going to IPv6.
   Another possible way to go is to deploy in a shared network.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [cloudstack] rohityadavcloud commented on issue #6298: Place VM's on the same network as the CloudStack-management server

Posted by GitBox <gi...@apache.org>.
rohityadavcloud commented on issue #6298:
URL: https://github.com/apache/cloudstack/issues/6298#issuecomment-1217983763

   It's possible to do this by deploying VMs on a L2 network whose vlan is `vlan://untagged` essentially you'll be on the same network as your host/mgmt network.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [cloudstack] nxsbi commented on issue #6298: Place VM's on the same network as the CloudStack-management server

Posted by GitBox <gi...@apache.org>.
nxsbi commented on issue #6298:
URL: https://github.com/apache/cloudstack/issues/6298#issuecomment-1176569986

   @CKrieger2020 - have you tried to create a new Network or create a L2 network (assuming your CS instance is on a separate L2 network than what is available in CS for users to choose from)
   In my home lab I have been able to create instance using L2 which talks to my other computers on the home network.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [cloudstack] rohityadavcloud closed issue #6298: Place VM's on the same network as the CloudStack-management server

Posted by GitBox <gi...@apache.org>.
rohityadavcloud closed issue #6298: Place VM's on the same network as the CloudStack-management server
URL: https://github.com/apache/cloudstack/issues/6298


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org