[Yahoo-eng-team] [Bug 1638399] [NEW] EC2 networking driver for Neutron
Public bug reported: OpenStack project is so far focused on private cloud management. This proposal together with a set of others for glance, cinder and nova aim to extend OpenStack for side-by-side management of Public cloud. Enterprises are increasingly looking at hybrid and multi-cloud strategy as next phase of their datacenter environments. Public cloud offers flexible on-demand resource while private cloud gives the ability to run workloads securely. There is lack of standard when it comes to cloud management. These specs propose OpenStack API as the solution. Regardless of infrastructure — public or private and technology — KVM, VMware or Hyper-V cloud workloads can be deployed and managed with standard OpenStack API. This driver will provide a mechanism to implement neutron networking on top of AWS. As was demoed in the Openstack Barcelona Summit in 2016, following constructs map nicely and work. -- Creation of tenant networks and all operations -- Creation of subnet -- Creation of router to connect external (public) network to tenant network -- Floating IPs. The draft code is available here: https://github.com/platform9 /openstack-omni/tree/master/neutron ** Affects: neutron Importance: Undecided Status: New ** Tags: rfe ** Tags added: rfe -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1638399 Title: EC2 networking driver for Neutron Status in neutron: New Bug description: OpenStack project is so far focused on private cloud management. This proposal together with a set of others for glance, cinder and nova aim to extend OpenStack for side-by-side management of Public cloud. Enterprises are increasingly looking at hybrid and multi-cloud strategy as next phase of their datacenter environments. Public cloud offers flexible on-demand resource while private cloud gives the ability to run workloads securely. There is lack of standard when it comes to cloud management. These specs propose OpenStack API as the solution. Regardless of infrastructure — public or private and technology — KVM, VMware or Hyper-V cloud workloads can be deployed and managed with standard OpenStack API. This driver will provide a mechanism to implement neutron networking on top of AWS. As was demoed in the Openstack Barcelona Summit in 2016, following constructs map nicely and work. -- Creation of tenant networks and all operations -- Creation of subnet -- Creation of router to connect external (public) network to tenant network -- Floating IPs. The draft code is available here: https://github.com/platform9 /openstack-omni/tree/master/neutron To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1638399/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1499064] Re: expensive port request on validate networks
*** This bug is a duplicate of bug 1521788 *** https://bugs.launchpad.net/bugs/1521788 ** This bug has been marked a duplicate of bug 1521788 nova.network.neutronv2.api.validate_networks could be smarter when listing ports -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1499064 Title: expensive port request on validate networks Status in neutron: Incomplete Bug description: On validate_networks call, there is an expensive call to retrieve all ports when only the counter is needed. On the top of that, it should check first if quota is enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1499064/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1593362] [NEW] Single Sign on Users must have an identity in keystone
Public bug reported: Single sign on (SSO) users from an external identity provider (IDP) are mapped to keystone group/user with a mapping rule. The identity of such a user is lost in context of OpenStack. Once the operation makes it to OpenStack services, only group is available in the context. This poses multiple problems 1. The owners of various objects like VMs, Volumes, Networks are not identifiable as that specific SSO user. 2. The user-quota api for various projects like nova, cinder and neutron does not work. ** Affects: keystone Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1593362 Title: Single Sign on Users must have an identity in keystone Status in OpenStack Identity (keystone): New Bug description: Single sign on (SSO) users from an external identity provider (IDP) are mapped to keystone group/user with a mapping rule. The identity of such a user is lost in context of OpenStack. Once the operation makes it to OpenStack services, only group is available in the context. This poses multiple problems 1. The owners of various objects like VMs, Volumes, Networks are not identifiable as that specific SSO user. 2. The user-quota api for various projects like nova, cinder and neutron does not work. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1593362/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
