[jira] [Updated] (CLOUDSTACK-10428) Add dynamism to Persistent Networks in CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pearl updated CLOUDSTACK-10428: --- Description: Hey There! To give you a brief overview: Users often may want to manage resources like Virtual Machines, physical devices, like routers, switches, etc, outside the scope of CloudStack. To ensure that such devices can be easily managed and provisioned, CloudStack offers Persistent Networks, which ascertains that the network gets provisioned at the time of its creation, unlike the usual networks, which get provisioned only after deployment of VMs on that network. However, today, we do not have a mechanism to facilitate automatic creation of the network on hosts that have been added to a cluster or transitioned from disabled/maintenance to Enabled state post creation of the network. Under such circumstances, users would need to either manually setup the network or deploy a VM via CloudStack to provision the network on specific hosts. It would be a nice feature to incorporate some amount of dynamism into CloudStack such that we can introduce a sort of a Listener to - Scan and identify if new hosts have been added - Scan for hosts that have transitioned to Active state post creation of the network and enable implementing the resources on such Hosts. And at the end of the day, end users are happy that everything required is already setup for them to deploy their resources - VMs. Skills required: - Java - MySQL More info can be got at: [https://github.com/apache/cloudstack/issues/4814] was: Hey There! To give you a brief overview: Users often may want to manage resources like Virtual Machines, physical devices, like routers, switches, etc, outside the scope of CloudStack. To ensure that such devices can be easily managed and provisioned, CloudStack offers Persistent Networks, which ascertains that the network gets provisioned at the time of its creation, unlike the usual networks, which get provisioned only after deployment of VMs on that network. However, today, we do not have a mechanism to facilitate automatic creation of the network on hosts that have been added to a cluster or transitioned from disabled/maintenance to Enabled state post creation of the network. Under such circumstances, users would need to either manually setup the network or deploy a VM via CloudStack to provision the network on specific hosts. It would be a nice feature to incorporate some amount of dynamism into CloudStack such that we can introduce a sort of a Listener to - Scan and identify if new hosts have been added - Scan for hosts that have transitioned to Active state post creation of the network and enable implementing the resources on such Hosts. And at the end of the day, end users are happy that everything required is already setup for them to deploy their resources - VMs. Skills More info can be got at: [https://github.com/apache/cloudstack/issues/4814] > Add dynamism to Persistent Networks in CloudStack > - > > Key: CLOUDSTACK-10428 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10428 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Devices >Reporter: Pearl >Priority: Major > Labels: gsoc2021, mentor > > Hey There! > To give you a brief overview: Users often may want to manage resources like > Virtual Machines, physical devices, like routers, switches, etc, outside the > scope of CloudStack. To ensure that such devices can be easily managed and > provisioned, CloudStack offers Persistent Networks, which ascertains that the > network gets provisioned at the time of its creation, unlike the usual > networks, which get provisioned only after deployment of VMs on that network. > However, today, we do not have a mechanism to facilitate automatic creation > of the network on hosts that have been added to a cluster or transitioned > from disabled/maintenance to Enabled state post creation of the network. > Under such circumstances, users would need to either manually setup the > network or deploy a VM via CloudStack to provision the network on specific > hosts. > It would be a nice feature to incorporate some amount of dynamism into > CloudStack such that we can introduce a sort of a Listener to > - Scan and identify if new hosts have been added > - Scan for hosts that have transitioned to Active state > post creation of the network and enable implementing the resources on such > Hosts. > And at the end of the day, end users are happy that everything required is > already setup for them to deploy their resources - VMs. > Skills required: > - Java > - MySQL > More info can be got at:
[jira] [Updated] (CLOUDSTACK-10428) Add dynamism to Persistent Networks in CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pearl updated CLOUDSTACK-10428: --- Description: Hey There! To give you a brief overview: Users often may want to manage resources like Virtual Machines, physical devices, like routers, switches, etc, outside the scope of CloudStack. To ensure that such devices can be easily managed and provisioned, CloudStack offers Persistent Networks, which ascertains that the network gets provisioned at the time of its creation, unlike the usual networks, which get provisioned only after deployment of VMs on that network. However, today, we do not have a mechanism to facilitate automatic creation of the network on hosts that have been added to a cluster or transitioned from disabled/maintenance to Enabled state post creation of the network. Under such circumstances, users would need to either manually setup the network or deploy a VM via CloudStack to provision the network on specific hosts. It would be a nice feature to incorporate some amount of dynamism into CloudStack such that we can introduce a sort of a Listener to - Scan and identify if new hosts have been added - Scan for hosts that have transitioned to Active state post creation of the network and enable implementing the resources on such Hosts. And at the end of the day, end users are happy that everything required is already setup for them to deploy their resources - VMs. Skills More info can be got at: [https://github.com/apache/cloudstack/issues/4814] was: Hey There! To give you a brief overview: Users often may want to manage resources like Virtual Machines, physical devices, like routers, switches, etc, outside the scope of CloudStack. To ensure that such devices can be easily managed and provisioned, CloudStack offers Persistent Networks, which ascertains that the network gets provisioned at the time of its creation, unlike the usual networks, which get provisioned only after deployment of VMs on that network. However, today, we do not have a mechanism to facilitate automatic creation of the network on hosts that have been added to a cluster or transitioned from disabled/maintenance to Enabled state post creation of the network. Under such circumstances, users would need to either manually setup the network or deploy a VM via CloudStack to provision the network on specific hosts. It would be a nice feature to incorporate some amount of dynamism into CloudStack such that we can introduce a sort of a Listener to - Scan and identify if new hosts have been added - Scan for hosts that have transitioned to Active state post creation of the network and enable implementing the resources on such Hosts. And at the end of the day, end users are happy that everything required is already setup for them to deploy their resources - VMs. More info can be got at: [https://github.com/apache/cloudstack/issues/4814] > Add dynamism to Persistent Networks in CloudStack > - > > Key: CLOUDSTACK-10428 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10428 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Devices >Reporter: Pearl >Priority: Major > Labels: gsoc2021, mentor > > Hey There! > To give you a brief overview: Users often may want to manage resources like > Virtual Machines, physical devices, like routers, switches, etc, outside the > scope of CloudStack. To ensure that such devices can be easily managed and > provisioned, CloudStack offers Persistent Networks, which ascertains that the > network gets provisioned at the time of its creation, unlike the usual > networks, which get provisioned only after deployment of VMs on that network. > However, today, we do not have a mechanism to facilitate automatic creation > of the network on hosts that have been added to a cluster or transitioned > from disabled/maintenance to Enabled state post creation of the network. > Under such circumstances, users would need to either manually setup the > network or deploy a VM via CloudStack to provision the network on specific > hosts. > It would be a nice feature to incorporate some amount of dynamism into > CloudStack such that we can introduce a sort of a Listener to > - Scan and identify if new hosts have been added > - Scan for hosts that have transitioned to Active state > post creation of the network and enable implementing the resources on such > Hosts. > And at the end of the day, end users are happy that everything required is > already setup for them to deploy their resources - VMs. > Skills > More info can be got at: [https://github.com/apache/cloudstack/issues/4814] > -- This
[jira] [Updated] (CLOUDSTACK-10428) Add dynamism to Persistent Networks in CloudStack
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pearl updated CLOUDSTACK-10428: --- Description: Hey There! To give you a brief overview: Users often may want to manage resources like Virtual Machines, physical devices, like routers, switches, etc, outside the scope of CloudStack. To ensure that such devices can be easily managed and provisioned, CloudStack offers Persistent Networks, which ascertains that the network gets provisioned at the time of its creation, unlike the usual networks, which get provisioned only after deployment of VMs on that network. However, today, we do not have a mechanism to facilitate automatic creation of the network on hosts that have been added to a cluster or transitioned from disabled/maintenance to Enabled state post creation of the network. Under such circumstances, users would need to either manually setup the network or deploy a VM via CloudStack to provision the network on specific hosts. It would be a nice feature to incorporate some amount of dynamism into CloudStack such that we can introduce a sort of a Listener to - Scan and identify if new hosts have been added - Scan for hosts that have transitioned to Active state post creation of the network and enable implementing the resources on such Hosts. And at the end of the day, end users are happy that everything required is already setup for them to deploy their resources - VMs. More info can be got at: [https://github.com/apache/cloudstack/issues/4814] was: Hey There! To give you a brief overview: Users often may want to manage resources like Virtual Machines, physical devices, like routers, switches, etc, outside the scope of CloudStack. To ensure that such devices can be easily managed and provisioned, CloudStack offers Persistent Networks, which ascertains that the network gets provisioned at the time of its creation, unlike the usual networks, which get provisioned only after deployment of VMs on that network. However, today, we do not have a mechanism to facilitate automatic creation of the network on hosts that have been added to a cluster or transitioned from disabled/maintenance to Enabled state post creation of the network. Under such circumstances, users would need to either manually setup the network or deploy a VM via CloudStack to provision the network on specific hosts. It would be a nice feature to incorporate some amount of dynamism into CloudStack such that we can introduce a sort of a Listener to - Scan and identify if new hosts have been added - Scan for hosts that have transitioned to Active state post creation of the network and enable implementing the resources on such Hosts. And at the end of the day, end users are happy that everything required is already setup for them to deploy their resources - VMs. > Add dynamism to Persistent Networks in CloudStack > - > > Key: CLOUDSTACK-10428 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10428 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Devices >Reporter: Pearl >Priority: Major > Labels: gsoc2021, mentor > > Hey There! > To give you a brief overview: Users often may want to manage resources like > Virtual Machines, physical devices, like routers, switches, etc, outside the > scope of CloudStack. To ensure that such devices can be easily managed and > provisioned, CloudStack offers Persistent Networks, which ascertains that the > network gets provisioned at the time of its creation, unlike the usual > networks, which get provisioned only after deployment of VMs on that network. > However, today, we do not have a mechanism to facilitate automatic creation > of the network on hosts that have been added to a cluster or transitioned > from disabled/maintenance to Enabled state post creation of the network. > Under such circumstances, users would need to either manually setup the > network or deploy a VM via CloudStack to provision the network on specific > hosts. > It would be a nice feature to incorporate some amount of dynamism into > CloudStack such that we can introduce a sort of a Listener to > - Scan and identify if new hosts have been added > - Scan for hosts that have transitioned to Active state > post creation of the network and enable implementing the resources on such > Hosts. > And at the end of the day, end users are happy that everything required is > already setup for them to deploy their resources - VMs. > More info can be got at: [https://github.com/apache/cloudstack/issues/4814] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CLOUDSTACK-10428) Add dynamism to Persistent Networks in CloudStack
Pearl created CLOUDSTACK-10428: -- Summary: Add dynamism to Persistent Networks in CloudStack Key: CLOUDSTACK-10428 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10428 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: Network Devices Reporter: Pearl Hey There! To give you a brief overview: Users often may want to manage resources like Virtual Machines, physical devices, like routers, switches, etc, outside the scope of CloudStack. To ensure that such devices can be easily managed and provisioned, CloudStack offers Persistent Networks, which ascertains that the network gets provisioned at the time of its creation, unlike the usual networks, which get provisioned only after deployment of VMs on that network. However, today, we do not have a mechanism to facilitate automatic creation of the network on hosts that have been added to a cluster or transitioned from disabled/maintenance to Enabled state post creation of the network. Under such circumstances, users would need to either manually setup the network or deploy a VM via CloudStack to provision the network on specific hosts. It would be a nice feature to incorporate some amount of dynamism into CloudStack such that we can introduce a sort of a Listener to - Scan and identify if new hosts have been added - Scan for hosts that have transitioned to Active state post creation of the network and enable implementing the resources on such Hosts. And at the end of the day, end users are happy that everything required is already setup for them to deploy their resources - VMs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
