[jira] [Updated] (CLOUDSTACK-8436) Computing offering with High avaliability does not work properly.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luis Henrique Okama updated CLOUDSTACK-8436: Attachment: JIRA-8436snapshot_template.patch > Computing offering with High avaliability does not work properly. > - > > Key: CLOUDSTACK-8436 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8436 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.4.2 >Reporter: Luis Henrique Okama > Attachments: JIRA-8436snapshot_template.patch > > > Steps to reproduce: > 1) Create any instance based on 'HA' offering, > 2) Shutdown the instance on XenCenter or via console (shutdown -h) > 3) ACS does not change the instance's state to 'Stopped', it keeps showing > its state as 'Running'. The HA restart of the instance does never takes place. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8435) When the ssvm agent restarts, every template generated from a VM snapshot disappear.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luis Henrique Okama updated CLOUDSTACK-8435: Attachment: JIRA-8435-HA.patch > When the ssvm agent restarts, every template generated from a VM snapshot > disappear. > > > Key: CLOUDSTACK-8435 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8435 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Hypervisor Controller, SystemVM, Template, XenServer >Affects Versions: 4.4.2 >Reporter: Luis Henrique Okama > Attachments: JIRA-8435-HA.patch > > > Steps to reproduce: > 1) In 'Storage' section, create a template from a VM snapshot > 2) list the new template on 'Templates' section filtered by 'mine' > 3) restart ssvm agent responsible for that zone (or reboot ssvm instance) > 4) try to list the new template again. The template is gone. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8436) Computing offering with High avaliability does not work properly.
Luis Henrique Okama created CLOUDSTACK-8436: --- Summary: Computing offering with High avaliability does not work properly. Key: CLOUDSTACK-8436 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8436 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.4.2 Reporter: Luis Henrique Okama Steps to reproduce: 1) Create any instance based on 'HA' offering, 2) Shutdown the instance on XenCenter or via console (shutdown -h) 3) ACS does not change the instance's state to 'Stopped', it keeps showing its state as 'Running'. The HA restart of the instance does never takes place. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8435) When the ssvm agent restarts, every template generated from a VM snapshot disappear.
Luis Henrique Okama created CLOUDSTACK-8435: --- Summary: When the ssvm agent restarts, every template generated from a VM snapshot disappear. Key: CLOUDSTACK-8435 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8435 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Hypervisor Controller, SystemVM, Template, XenServer Affects Versions: 4.4.2 Reporter: Luis Henrique Okama Steps to reproduce: 1) In 'Storage' section, create a template from a VM snapshot 2) list the new template on 'Templates' section filtered by 'mine' 3) restart ssvm agent responsible for that zone (or reboot ssvm instance) 4) try to list the new template again. The template is gone. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7995) Cloudstack user can create and manage shared networks in a simpler way
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luis Henrique Okama updated CLOUDSTACK-7995: Description: Originally in Cloudstack, only the root administrator is able to create shared networks, since it requires a full understanding of the topology to provide accurate information about the new shared network, e.g. IP range, netmask, gateway, VLAN ID and so on. GloboNetwork network plugin provides a much simpler way to create shared networks, allowing a regular Cloudstack user to create and manage shared networks by providing name, description and zone/environment in which he or she wants it to be deployed. This is possible thanks to an external open source API called GloboNetworkAPI. The open source 'GloboNetworkAPI' provides a simple way to manage multi-vendor network equipment, including routers, switches and load balancers. It is responsible for automatically creating and removing VLAN/networks, allocating and deallocating IP addresses, applying load balancer rules and many other features and is equipped with a web interface to easily manage all these resources. This proposal includes both the GloboNetwork plugin and the API client to greatly reduce complexity when dealing with shared networks and allow an external network hardware to act as router instead of a VirtualRouter. Design Document: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Regular+cloudstack+user+can+create+and+manage+shared+networks+by+GloboNetwork+in+a+simpler+way was: Originally in Cloudstack, only the root administrator is able to create shared networks, since it requires a full understanding of the topology to provide accurate information about the new shared network, e.g. IP range, netmask, gateway, VLAN ID and so on. GloboNetwork network plugin provides a much simpler way to create shared networks, allowing a regular Cloudstack user to create and manage shared networks by providing name, description and zone/environment in which he or she wants it to be deployed. This is possible thanks to an external open source API called GloboNetworkAPI. The open source 'GloboNetworkAPI' provides a simple way to manage multi-vendor network equipment, including routers, switches and load balancers. It is responsible for automatically creating and removing VLAN/networks, allocating and deallocating IP addresses, applying load balancer rules and many other features and is equipped with a web interface to easily manage all these resources. This proposal includes both the GloboNetwork plugin and the API client to greatly reduce complexity when dealing with shared networks and allow an external network hardware to act as router instead of a VirtualRouter. > Cloudstack user can create and manage shared networks in a simpler way > -- > > Key: CLOUDSTACK-7995 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7995 > Project: CloudStack > Issue Type: New Feature > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation, Management Server >Affects Versions: Future >Reporter: Luis Henrique Okama > Labels: features, globonetwork > Fix For: 4.6.0 > > > Originally in Cloudstack, only the root administrator is able to create > shared networks, since it requires a full understanding of the topology to > provide accurate information about the new shared network, e.g. IP range, > netmask, gateway, VLAN ID and so on. > GloboNetwork network plugin provides a much simpler way to create shared > networks, allowing a regular Cloudstack user to create and manage shared > networks by providing name, description and zone/environment in which he or > she wants it to be deployed. This is possible thanks to an external open > source API called GloboNetworkAPI. > The open source 'GloboNetworkAPI' provides a simple way to manage > multi-vendor network equipment, including routers, switches and load > balancers. It is responsible for automatically creating and removing > VLAN/networks, allocating and deallocating IP addresses, applying load > balancer rules and many other features and is equipped with a web interface > to easily manage all these resources. > This proposal includes both the GloboNetwork plugin and the API client > to greatly reduce complexity when dealing with shared networks and allow an > external network hardware to act as router instead of a VirtualRouter. > Design Document: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Regular+cloudstack+user+can+create+and+manage+shared+networks+by+GloboNetwork+in+a+simpler+way -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7995) Cloudstack user can create and manage shared networks in a simpler way
Luis Henrique Okama created CLOUDSTACK-7995: --- Summary: Cloudstack user can create and manage shared networks in a simpler way Key: CLOUDSTACK-7995 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7995 Project: CloudStack Issue Type: New Feature Security Level: Public (Anyone can view this level - this is the default.) Components: Automation, Management Server Affects Versions: Future Reporter: Luis Henrique Okama Fix For: 4.6.0 Originally in Cloudstack, only the root administrator is able to create shared networks, since it requires a full understanding of the topology to provide accurate information about the new shared network, e.g. IP range, netmask, gateway, VLAN ID and so on. GloboNetwork network plugin provides a much simpler way to create shared networks, allowing a regular Cloudstack user to create and manage shared networks by providing name, description and zone/environment in which he or she wants it to be deployed. This is possible thanks to an external open source API called GloboNetworkAPI. The open source 'GloboNetworkAPI' provides a simple way to manage multi-vendor network equipment, including routers, switches and load balancers. It is responsible for automatically creating and removing VLAN/networks, allocating and deallocating IP addresses, applying load balancer rules and many other features and is equipped with a web interface to easily manage all these resources. This proposal includes both the GloboNetwork plugin and the API client to greatly reduce complexity when dealing with shared networks and allow an external network hardware to act as router instead of a VirtualRouter. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7849) sort the projects on drop down menu alphabetically
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luis Henrique Okama resolved CLOUDSTACK-7849. - Resolution: Fixed > sort the projects on drop down menu alphabetically > -- > > Key: CLOUDSTACK-7849 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7849 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.3.0 >Reporter: Luis Henrique Okama > Fix For: 4.5.0 > > > It should have some kind of criteria to show the projects on drop down menu. > We change the projectSelect.js to sort the projects alphabetically. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7849) sort the projects on drop down menu alphabetically
Luis Henrique Okama created CLOUDSTACK-7849: --- Summary: sort the projects on drop down menu alphabetically Key: CLOUDSTACK-7849 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7849 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.3.0 Reporter: Luis Henrique Okama It should have some kind of criteria to show the projects on drop down menu. We change the projectSelect.js to sort the projects alphabetically. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
