[openstack-dev] [puppet] [infra] adding a third scenario in Puppet OpenStack integration jobs

Emilien Macchi emilien at redhat.com
Tue Jan 26 23:17:34 UTC 2016



On 01/26/2016 05:05 PM, Matt Fischer wrote:
> Also +1 for ceph
> 
> And Fernet is a great idea, Keystone is moving towards a day where it's
> default.

This is an etherpad in which we can brainstorm of the scenarios we want
to test:
https://etherpad.openstack.org/p/puppet-openstack-integration-scenarios

Feel free to connect and contribute,
Thanks

> On Tue, Jan 26, 2016 at 2:20 PM, David Moreau Simard <dms at redhat.com
> <mailto:dms at redhat.com>> wrote:
> 
>     +1 for adding puppet-ceph and Ceph integration in Nova, Cinder and
>     Glance.
> 
>     This means there would be two scenarios involving Cinder (lvm+iscsi
>     and RBD) and three scenarios involving Glance (file, RBD, Swift)
> 
>     I find it redundant to install components in the same way across all
>     three scenarios. Perhaps we could have a keystone with fernet tokens
>     in one scenario and another backend elsewhere.
> 
>     I'm only familiar with KVM as a hypervisor but maybe we could also
>     throw another one in there (Xen ?)
> 
>     David Moreau Simard
>     Senior Software Engineer | Openstack RDO
> 
>     dmsimard = [irc, github, twitter]
> 
>     On Jan 26, 2016 12:06 PM, "Emilien Macchi" <emilien at redhat.com
>     <mailto:emilien at redhat.com>> wrote:
> 
>         Hi folks,
> 
>         Puppet OpenStack integration jobs [1] are very helpful to perform
>         functional testing when deploying OpenStack with our modules.
> 
>         We current run scenario 001 and 002 on both centos7 & trusty,
>         which is 4
>         jobs in the check queue.
> 
>         I would like to propose some changes, feel free to comment:
>         * a complete scenario with ceph, using openstack/puppet-ceph
>         integrated
>         with Nova, Glance, Cinder and eventually Gnocchi.
>         * more Neutron testing: LBaaSv1 first, Octavia in the future,
>         FWaaS, VPNaaS.
>         * more services: murano, mistral, manila, designate
>         * switch from ipv4 local loopback (127.0.0.1) to to ipv6 local
>         loopback
>         binding.
> 
>         Those changes would probably require one more scenario, which
>         represents
>         2 more jobs. Adding [infra] tag here so they can weigh on it.
> 
>         Any feedback is welcome,
>         Thanks,
> 
>         [1]
>         https://github.com/openstack/puppet-openstack-integration#description
>         --
>         Emilien Macchi
> 
> 
>         __________________________________________________________________________
>         OpenStack Development Mailing List (not for usage questions)
>         Unsubscribe:
>         OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>         <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>         http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
>     __________________________________________________________________________
>     OpenStack Development Mailing List (not for usage questions)
>     Unsubscribe:
>     OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>     <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 

-- 
Emilien Macchi

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160126/d691aec6/attachment.pgp>


More information about the OpenStack-dev mailing list