Re: [openstack-dev] [murano] Berkshelf/Chef/Puppet installation on Murano images
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2/26/16 6:35 AM, Olivier Lemasle wrote: > Hi all, Hi! > Some months ago, I started to work on a Murano integration with > Berkshelf [1] to manage Chef cookbooks dependencies when Murano deploys > a Chef cookbook (cf spec [2]). This is awesome! Thanks for this. It's crazy thought, we have the openstack-chef[1] project, why didn't you spin it up there? > However, I still haven't finalize the work with the integration tests > (review on hold [4]) because it requires having Berkshelf installed on > the image (and the latest murano-agent). > > I still wonder what is the best way to install Berkshelf. That's up for debate, you mention the chefdk lower in the email, it maybe the way you want to go, but there are caveats. > Of course, we can install Berkshelf in Murano agent DIB elements. But do > we really want this additional software coming up in Murano images even > if neither Berkshelf nor Chef is used? Probably not, if you've bootstrapped the image to be what you want and chef isn't used anymore then no. But the advantage of having chef there is the ability to have it check in to the chef-server and update/change the configuration over time. Unless you're just planning to rebuild the image every time. > An other solution is to install Berkshelf at runtime using cloud-init, > like Henar Muñoz did for Chef and Puppet last month [7]. However, I'm a > little bit confused by all these solutions. Is there a recommended > solution? And which solution should I use to make my functional tests > work [4]? Cloud-init isn't great, but you can pull the chefdk down via it then hand it off to chef to finish your bootstraping. Remember chef can be called at any time while cloud-init is only called on creation...well not 100% but that's the majority of use cases. > Any thought? I'm interested to see where this goes. Maybe we should sync up off list and talk about this more, I'm here to help so don't hesitate to reach out. [1]: https://wiki.openstack.org/wiki/Chef - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJW0HGdAAoJEDZbxzMH0+jTLFkP/iQfTjNdG6aXF+eKFE2iKPo0 rUIj5D0c/chzTX+lrV49KrvJoDkjjSVelDP/B3CMOGZvhmXtluOZ+o0igM5Vq2Tt xJvxKkHVE/yNqTSbBJrsdCJ6Mtr+BZL4rZvvWoN4NOd9ocUCMWvPin15lZDmbPE3 CIYaEXiQ4eVHYaTJgtij6YGww8y7Uk2xFDXxqsw0akPTgRUe/Ui0eeZqcJQLraVN T2vgAbGgjlp8rlphUms3jhTyitAvZ7T7TVMd84iBvgIfsMH/audLDyqas/8Sb14P 1i3GRywTXvz1SKEl+SBqSYfsI1tLeQZvL5zIxBe4Ds/eLw37lsyLrvoEIu00p4Qz zQAcez1jBN8DMhenzHJQTdB9JKo7VP8hGCWem9UD3Q6IxjMUVHg6m8L2vHqpYSBz Z9+597SAHo+UK+hXynHBAyQ4CVJ+mZ1GnWhIewlSke2DM0X/65Ye/k0figMk4Hf6 LfN38Lqqb49LHySSeMMNle5lF9FAUGeCI949SZL54kp+3yPLS6QpMUZ84hA9eI95 7webdSoO5TP/fpUWi6jwEOTjSIdtWZQnbFk+WOeP/RKd+IUCe4MEij4Y/RxAYZSd zkpxhUHImmteMuy2kDK7O7+KWMgm4ddWgFzSQQOGVCCoF99i/MJndRS3K6eadtbY SAI0iY56aSRHpa7dyzVv =E1YO -END PGP SIGNATURE- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [chef] deprecation and removal of old branches
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 1/6/16 10:22 AM, Samuel Cassiba wrote: > I'm +1 on this idea. Looking at other OpenStack projects (Nova, Neutron, > etc.) on GitHub, they only have stable/liberty and stable/kilo Sounds good to me too. - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWjbnBAAoJEDZbxzMH0+jTbTcP/i/RbxfmQ2T3wasWUKLup9Y3 bbsiUcfocw40ZT2Y/i/fLiH+mGfIRcvXTLMkYdwji7jhoes2Vt3l+S/CmDR9kb59 hqxiIft/6kfW3JLjtjkAZtZ5xwa+QSN8DY4aZnnVU9mjdCgDH0DZRuwOZcERZH0Q 6gQeIFp0udGVLfDaF32mEdKRRbSlRil6reciDg6W7g+/1lCys8H7ig0/5rqQxE0o GmKxyGOlEnpPjpVQz1JeBadktHNjRPOJ1ihiHmC8XusMdg0FDppiJUmLd8gmLFNY hRpD2QFHjzlsy+7u5chsiN+ctjawuEZsHCeDD3UDAiSQjptHQy8jw7gl+V4nQry6 SSpRYkdfV8k5Pf3nsJ8Yyt0SqYggnqjok7DQ9VxEiLdMyQbG+DE7CQI6w/TxmniC oiScygu8dCh+KUZ7OXUSBWquHWln6eQlWgJNqv/o4UxZJl9NLxkhDU7OgvMvvCjl I1Gx2BdNIcknZhG3KfzUfj1j97whVJkJyHvWMem+pj2BXFY3eIcAkHKx9nHO+cNy hBFWoCUXGJHxsUMHhDH7FhbuvQR8qCHVaRvmMaKMyO+6S+5R1Q/L4dYvxZjHNScn 3JcWaC5+k91Acj6DYrv4hxszUBtM+KpyG/13Z9ed+qwd6QxH8beKD82kES1ZEl+P crT1uNDOT9ToRLWRHEwd =2adb -END PGP SIGNATURE- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [openstack][openstack-operators] Starting with Jenkins and jjb/OpenStack Board of Directors
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hey everyone, First off, I've looked around and there are some great tutorials on the jjb and Jenkins. The problem I found was that there isn't a "lets start from scratch" type tutorial. I tried to fix this with this simple how-to[1]. Hopefully it's easy enough to get someone who is gun shy with starting with the jjb to take the leap. Secondly, if you don't know, I'm running[2] for the OpenStack Board of Directors as an Operator and attempt to represent the Operating Community on the Board. I'm going to attempt to campaign using, the mailing list, twitter, probably linkedin and the like. I'd love to get your vote. So, please, if you have voting rights next week please consider me. If you would like to help me out tweets, or emails to colleagues are probably the best way. More people posting and voting will help get the buzz that we as a community needs. Here's a example tweet if you'd like to copy and paste ;) : I’m voting for that @jjasghar, he should be on the #OpenStack Board of Directors! Read his reasons here: http://bit.ly/JJ-4-OpenStack-BoD-2016 Thanks for your time, and if you have any questions don't hesitate to reach out. [1]: http://jjasghar.github.io/blog/2016/01/03/getting-jenkins-and-jenkins-job-builder-running/ [2]: http://bit.ly/JJ-4-OpenStack-BoD-2016 - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWitfkAAoJEDZbxzMH0+jT8m8P/A45LznC6FGktg0llm7SO4Pk dsIRTIxi8HHjHegSzjlaeDK+G3wN+JcmrWLh0r5dVcnYf7VSHYtHKet7uBtCRko2 4wgvnZDWbNcyKu4bIpUTQuBCcoPowlVZiMXYiFUxAUvoV196O72aZVfj62UCRUNf kbhG1JgOXMyOGiiB9zY41tuiu6UvnBJQkJ86VnbEJiVcThPAhRPpf6KgVgg/bi/h b45ZHHCbXU7CJ1wx+qFOZznA1ntSzhF5SIflwUhJfAkC7IrFZYp6rvSltYgInbIN KC1G2eS5AxU5cUrKacDf+07fpi30LmVDb3RmIu+WATJiSTb0ImGKupLYRyMVaUC6 FUBSyBuqSctX2ifYPAGKV3UmNaCfvO8I+LeEj6o+lkAO+C+5EGECJmTH30JyatsZ Bs2eSvJjXxRdTQX5ztekPFV8q9uuoTX3+CLFQUfYU54iuG/9B4a/3GiiZm8A0vWE nMRP2CER5HICn9WmDlygfuauPW80lyfZJe2BGAt+f2byg6e3cDNsHI9rJvKCKu6Y vA+HBfOj/7BUA87ppfbzpzIfXPmQ3hg8xPZuliR071Nh7J/wh8WyerkVHaYt9Mu9 J1rf7wrEFw+9E0xrFZpXdxEAC7nklU5rRXa4fCX2OJTzdy8VTpIISfeXfEg5YX0K rFHZ4sQO/rjOpggylG5u =QqNc -END PGP SIGNATURE- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [openstack][openstack-operators][chef] kitchen-openstack 2.2.0 released!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hey everyone! I just released 2.2.0[1] of the kitchen-openstack driver. If your curious the CHANGELOG is located here[2]. We're doing great work with kitchen-openstack, and would love to see some more feedback on things the community would support or features. Please put in an issue[3], for a feature request, so we can start the discussion there. If you have any questions or thoughts don't hesitate to reach out. [1]: https://rubygems.org/gems/kitchen-openstack/versions/2.2.0 [2]: https://github.com/test-kitchen/kitchen-openstack/blob/master/CHANGELOG.md#220 [3]: https://github.com/test-kitchen/kitchen-openstack/issues - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWcbXfAAoJEDZbxzMH0+jT5S0P/RRHbahe0rMnzHNuiPtThilg JODMMoHR0MmGsis/n3CSZ4WDez7Ev558Ph7iqx8upuHL3Asa/zreaK4fOlrjvDeW WVopRa0myKVZpTssnQXNP6ZFRWcrr2nQaL8CXkk+r2ULVG64M+b/ekYfGrdOUfuw zcNQoM6Z9vRGflPjD3WDLVDpVw2awRrZQ3AOanpPyxiIZMvVbQodJYnhBXA9pSlQ lXgC9qG/JPhq3VYuAocLofiF8+maIvCUB6EU9i0ddfaqBMyiFrPo9l0RYaNIMQXF f+b1WdDq5vRi8RJSl4v9TEWpaqF+spHpFqA2GS6LSeh1/Wv9R2+/xKS1C1jrAfMn Zh29jb324tpJ6A/783+1C7+Psa6V2d8Su8I0Fr00brWovdhag7pmKliHLyWTA78A a7wQtWohvalzGwjTofOkkbiY4IpIrwESUsOaT1pR+Gk0KZDt+s1+cwiU802IK6u1 eiCbXPOqho0Q0GNglFgVHbk/U2TqG0Z4+KV6utCCqOK9dkVJuGV5RHJ0IddEiXEr fvZbDVIkSozWbSsJBpKZuFOcT/XWc9UUCk/ow1FdlmxDN4o8CUcV5fliM/Y0AjXf Vh+wt9gfQNpv1Svhw+bhtjQiGoy5wkUOfT3QjE7D3Z7DFXcmmZqyh38YEDyiflZw 7Z031uewvalMgHRTeLGm =7kGh -END PGP SIGNATURE- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Rally as A Service?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11/24/15 1:35 PM, Munoz, Obed N wrote: > Is there any plan or work-in-progress for RaaS (Rally as a > Service)? I saw it mentioned on > https://wiki.openstack.org/wiki/Rally I think we've talked about something like this at the Operators Meetups. But this[1] is more or less what everyone just defaults to. [1]: https://github.com/svashu/docker-rally - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWVOCjAAoJEDZbxzMH0+jTo9gP/18pkAs9FMiL9qIWADZ5Q2BH bZlnIud0Yk5Qj9uVx3o+/Tk9OpFcDQy49FLZ1ytQD2hJeP+51Bk/JRSRCYW+GVo1 D4qlzu5FiQBDFIEn4YB4n2x1v7DrrxR9ADb5CjADdFf1RitkHJXSMXdh0XO+yO5n BWCDpIq/dVced2jMT4FhNDyArwgKrO/KMMbDaYG1TZueMXdU6JCMbshUOKkWiF1j 8hK8ergjzo/FDwv98NnD5cYbizPee1IgTBjsfaLO+PYmrKjU6qZrEqndabrnkPnQ DKSu+xxq6q8SzHnB/tQgJDfOMJkwtr8qk7wMHquzbVNfiNYcR6Yroke1C+QdPtwQ rVCcU6pLy2hNGQXvZpSWtXLe5PMohwQsCxHrWUtyB/DbUD5Eu1BetfCwSkBJCu2c 6m7KG+fMOwlEXmhUUQYDjrKBg8NkIFWwGXpNS3ITWekb4jkVyR3NG9Pr++yzTp0f nMR0vSaYn7xFgMJbJuO2jCsv2PMZ2SGt87CPnrbI5Hry9gyqw1D/u9jEamxtNCMU MOG0nDP+fWfiTuDXlVPOr4YeHyTYOWPWtGedj+f4jXIjiQ2e/Y6VXqWynfGQZXUX 12zgk11poOM8O9rgAQ+PHJpJqnZV5jhj4jyG+av9D+pm3kQxIgIXSLLnb4e5Kh+d 2yfcHXS5+Cgly28F+NMZ =V7wA -END PGP SIGNATURE- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [designate][chef] cookbook-openstack-dnsaas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11/23/15 7:17 AM, Hayes, Graham wrote: > On 20/11/15 21:23, JJ Asghar wrote: >> I walked through the developer install guide[2] and automated >> the build. I'm posting here because I can't find a "production" >> install guide, and was hoping that maybe someone will point me in >> the direction of the diff between the two. > > We have a guide for Kilo [3] - we are working on the liberty one > currently, but there should not be a huge difference. There is an > additional service (designate-zone-manager) that should follow the > same init / usage style of pool-manager, and we now support using a > tooz backend for co-ordination. This has only currently been fully > tested using Zookeeper - but as more tooz backends get written the > list should grow. > Awesome, thanks for this. I'm walking through the diff between them, and making the necessary changes. >> Would the designate team like me to come to ya'lls IRC meeting >> to talk about this more? > > Definitely - I can add it to the agenda for this week if you like? > We meet on Wednesdays @ 17:00 UTC in #openstack-meeting-alt [4] Awesome, I'm there, and yes please put me on the agenda. I'll take any questions and speak a little to the goals i have. See you on Wednesday. :D - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWU16GAAoJEDZbxzMH0+jTVGcP/A3r5B/KfavS8svOj9AQsuWJ lYu0YTkVaGv/PqaWAZzd+LR1UN/AO1zSpJTuSnIzBqKV7ivzad+CceVOqo1urdg0 hXUDKhlABQbBGhwpvMAkxfpmJRbvFN6EkZSkzGW4suOoawNWnfCpaAmHgAARZZyW lMGPO3MfL1fRLud6HZaijyoojFrmZYnI9pCyhNlFgqrjvRYVpCYN40nrrjmKaG9w If6oe8De85zDso87pkfXBGz7ebhB1tDiLlek0qer8j/raLk9n/VQB4Eg6q5UEaOq cWFPMuPvRGusquTZqtbMPOTzOtA9FNLvIomOBenIlXrvf765eoocqb4t0c7wx+a+ ivXkkoX9qqN+pCuNfXOJqqtE2KLIT7m4sFLFOHc+ZiVVRuKmXO5IG6eHeMtOdqHi qx/liXeuc61uRWlUA4PtlFfB85NVvOTF4KGIkWBGfDagtTnY1+W0HbDB+eO4RAZM ZQAA+6rIiaRfrl3D6KOXeYgTForkFHUm5TxKy+SvfVG+FOcvHwIfKSjRsDzRPxFi AQyX5hEoh7esZEevPsZGFjNbADJ4+X2ZDMPNHT4hTsAtMh59Zmu80q/5dEcZaBhN avUMadDJq0Ukh1Rjf62ShRswRTSWaXbyBzHuVeW5TjhzLLhW3vhPGQ/AvbmdpKBL Z5ozBrbjDxNOAjPsEQdE =00JB -END PGP SIGNATURE- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [designate][chef] cookbook-openstack-dnsaas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hey everyone! Per our goals for the M cycle, I've started cookbook-openstack-dnsaas[1]. It's under my namespace for the time being; but shouldn't be much longer. I walked through the developer install guide[2] and automated the build. I'm posting here because I can't find a "production" install guide, and was hoping that maybe someone will point me in the direction of the diff between the two. For the community as a whole though, after we get this "publicly" released, you'll be able to do a `chef exec kitchen verify` and you'll have a vagrant box with Designate built in just a few minutes. Would the designate team like me to come to ya'lls IRC meeting to talk about this more? [1]: https://github.com/jjasghar/cookbook-openstack-dnsaas [2]: http://docs.openstack.org/developer/designate/getting-started.html - -J - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWT434AAoJEDZbxzMH0+jTRi8P/0YCBDqFjAJqxNH1b7DFIKNt iWlPr8jyw0x7LXKAJdcJZ+vnnKjMzm9KMxhPsAPKN6M/WIupMdflJ1buOC1QWBlK AoeIEdriTHZJWIz6yBkev+kxhBix73FvpGTIvknLTM6vhuKWIHONSbcYv+PeuzUb kmCUhrnCMR4bHvaj3Z9wv1ECqkZJXcUP4gNVQxQ0sq7ibqsXXDis3o8WtXGt0iFT 22qc8csw4Apeh+THiDM4GY0hvg01Cf/osUDJcGZJrtDzBqsCOlSAWZHwF9O6nxEX m6qm0DavT2yiuvdb4rQ1KyisdsVR7MQeDlrzpy2Pb3AIWV7mag6q041YzRlp3dUa 3SgdcGhia/+GPKaXeRir9f17WuUrTAEd2sf6aCzDkXMCxdIhSR3it23w1QKVKaEm WfA3fqUBOCcpQkPO7Pw+jVvQTaVl/vzCPugizZjmM3rJXLRLQlOZYbpS30tG2WOD g6PXPrgR3YnDmMorZ1kH5ZRDhuQWumhVGnXCgRHZ0ipL/fp1Bbgjxj3DrCUJYKOg PrXkBF2BewYNAZSBHm+U8J3p4e+vdhhBfQSjQo1gHTolv3vL5MfCeDnzv3ZbZWeM 4fBxgl4ibZb2h9+Puc86BmWmCRQCMxyffNfDbCQUuG1ml6yhxsCna2BFxI5VS8fh 2IjbFf1X72dN9tEaJenL =lISg -END PGP SIGNATURE- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [openstack][openstack-operators] IRC meeting(s)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hey everyone! I've been seeing some interesting regressions in our community recently. Our IRC meetings, or at least the ones I've been attending, are extremely variable in quality. I believe this is a disservice to our community as a whole, so I've offered to help. I've written up a blog post[1] on some general characteristics of IRC meetings that seem to come out with the most fruitful conversations. I hope everyone finds something useful from this post, and hopefully will help educate new comers to our community in some good working practices. I'd love to talk about this more, so please don't hesitate to reach out. [1]: http://jjasghar.github.io/blog/2015/11/18/characteristics-of-a-successful-chatroom-meeting/ - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJWTRbiAAoJEDZbxzMH0+jTF4QQAKlso2UFCC79Rsxf2VR5gEMl 0i3n1aMmdnUB9Gz9yniaaoGBn4Vu0Xwx7jFdv2K3NGHDkvYl3NLEy9Z2nCgo7Pj4 b8CFmNrdEKx5mYHmg/7nRFm6VZC4OKyF2df5qByWOjreYdP9/s2hmqH97oLeQfyc Dd87PJlcvCzbgUONHyVJXioeWh6apqyuz+kr5l4hdyzYHeK490DfpzcRIMSuYWxW g9GPbEqSwEdSsiB1Z4OyYqV3BCOiLx1utJAgfwgC6K4ORO9g06eWP+I9RO3Ytz87 hU/HySoFqods0xj8uCwuO1TuFJEvF+Mw9xKhxg0bSRVGalnTE644H3kRpnaAyoZi Wqlz0/kKuCpEVdGe14adfeHYXsFhqYx2740SJ5hmsRUkK+XlZv+VSNnCPwDFkpyR Gz6aiReFTRw5HFSvuwNMQ/Ph4RcR0WBZraFyGPVnghMGgEkH8LCMRT+YR01oyU/G d23+qti9RF8z+7dnvH2auI+mc3cE6gWsRi40tPQmvcm+B7GBkTl66U0sBYbnVSsD Yyn/E/mnUmb6Ewzv8sDyKqIBS3U2iiR5dG36egN6H0R1ciroYEtk76ZdpHnfVsyw 9SsRdpWPbU3KjfR0pwwMyJAm40OUA0qjhTMXv20OEn7ocDlFUTa/ky/yMfx1XUPy YiPtOE0FOyAf/P59AR3a =bmr5 -END PGP SIGNATURE- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [openstack-operators][chef] Pre-release of new kitchen-openstack driver, Windows and 1.4 test-kitchen support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Everyone! I'd like to announce a pre-release[1] of 2.0.0.dev of the kitchen-openstack[2] driver gem. I've been able to test this with Windows 2012R2 and all the flavors of Linux I have on my OpenStack Cloud, but would love some more feedback.[3] If you could give this pre-release a shot, and post any issues, negative or positive; I'd like to get this pushed out to a real release late next week. (Sept. 17 or 18) If you don't know you can install the gem via: `gem install kitchen-openstack --pre` Please take note, with 1.4 TK, there is now a transport option for the transport driver, so you'll most likely need to add a transport section to your .kitchen.yml. I've made note of this here[3]. [1]: https://rubygems.org/gems/kitchen-openstack/versions/2.0.0.dev [2]: https://github.com/test-kitchen/kitchen-openstack [3]: https://github.com/test-kitchen/kitchen-openstack/issues [4]: https://github.com/test-kitchen/kitchen-openstack#usage - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJV8MaQAAoJEDZbxzMH0+jTCYUP/iUEqNG3WOZ6VJjuZCBO+4Wt 5h2DSvg7Tc7gB+IIUyvz8G++ymatvGyY9zRNhxCJcpQuwndxrfYJuVFB+2KiJ8hS oVfHcggVms0/DlmGUn8Lr/8GdCCawU2qwjkYg1STJorXCwH6phh6dIhWcPSjus8r f2/JKStmawFqQ7MW/hI5qvJ2o46AvfHEbzyPChD9YYNMffdZzrUfKVNL9JcCpl4+ N9VU+Y2e2oo1yjKro68tM7JR0qE5gF5k0BgRXcxWkSzPVLB+ilD+mAqCwoaaRmkr yuxAgWV7kwFWXQnK8O/OJEEX4/EQx6QqC7oR36DrPLGafxW9Jk9Jyj6eh12mt7G9 /uEAuKcket5F6CNLYikGH3Lm7ZhaFD75Of/9ourVWZy4aTl3zX7PaC7SwSb6Yx9B Flt4O4hf4Nl7PgPzf3kyuWaR+39HmEpF4WwCNQ+NdA92IKebDcsR6SgdcwxxkiOl 5wXhSs8vr+fgEGBYp4ZoEHmGUMWghd/fcoH5yDVt+neM1FB9wJwQAjMUV0z3kCJ1 AEyzwyNHTtflsnL3613//zwWTjKE9U3cHhY7KaiBrL2jO+rDsfi1cAD34usYI1G0 T76D9IAkxZz4TycGWgVzSVTY1ESqJFIxE2BLGeCDHZq/8fQsa7ZlrKif02V/eO+o jMSXjkVcXHATaMqFIMNe =f+U2 -END PGP SIGNATURE- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [openstack][openstack-operators][chef] stable/kilo is born!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I'd like to announce that we have stamped stable/kilo. I'd like to congratulate everyone who has committed and helped the OpenStack-Chef project get to this milestone. We have made tremendous progress with the limited resources our project has. If you are using or are thinking of using the Chef cookbooks please don't hesitate to come round to #openstack-chef and help out, our project is always looking for feedback. If you don't know, our meeting time is here[1] and most of the cores are available in the channel during US business hours. [1]: https://wiki.openstack.org/wiki/Meetings/ChefCookbook Cheers! - -- Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar irc: j^2 -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2 Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJV36LqAAoJEDZbxzMH0+jT1OAQAK6p7Z8HfBPiLuAvyWGDhF2Z MOVibLXXTjpZjdvUPwGo/nadVxUH5yZxUndZ8P6rmHcklvK0M6ETL6n3X86Y1rmG JbOf0oi7b2irIG50i+TCSdmhhelpDI/8tg+oFVD27nsTvfz1hNmlFjMNin7N1AD5 yqft1UJOU23B643F6/KCG299thyJviDN0Jgoe3VrKERXpol/1yL63VbNQOsLj6Dq 03hTGOW84qpUK8o+C+/7sxQ5KolrQ6OhYU4IBXafroiFtzeV8ROUX8WsrEtGXwzi RsQk2n0xlENy9XVIyJxKdoZx6VGSqvTKIMyF+9C42rvlBS0aRYUmnDR1u+vdGmWX H1bCUxbam0zG4GZ96GOXJ6xOlay79+qEIQt1svCIFeCxTmmLoFTLjQkAbSR+tf9W Cdys/+Pq2EZA/KG7CIMk6rAl/aveikO/9JoCuzyY7asm2++o0Csc1QoPvJU9MWHY mQHsonsf9MTd3/8cM7H7BnzWcGpbQYokhVwEJBaysqJekIrcJ8I+is87yEV9RuHB GtUCW84z2/+PwDYPSCZH+iE8eqY1Q7xyFRxzceoqZDtEaWjgmv73MTsnAZhza4Il GgdwFmLuk5UeKSfGTA7a5ernvCOHmoGmnD2mXKvqq5KnYw9X2cm69tZ5NiixVTZw baN5uo04PCDLGGzitSPJ =/MCc -END PGP SIGNATURE- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [chef] Restart service when package changes but config doesn't
On 8/10/15 3:11 PM, Ken Thomas wrote:
Hi all,
Hey Ken! (we miss you at our IRC meetings :) )
(I've been away for a couple of weeks and I tried to send this before
I left. I didn't see it come through so my apologies if this is the
second time you've seen this.)
Nope, this is the first time I've seen this, the [chef] tag isn't used
much so it's nice to see traffic.
I recall markvan mentioning a while ago that there was a need
for services to restart when the underlying package changed but the
config file didn't. We've got something in place and working that
does exactly that. I'd like to get y'all's opinion if it's an ugly
kludge or something useful that we might want to refine and contribute
back.
The basic approach is to look up a given package's version at
recipe compile time, and then again at runtime. If the two values are
different, then we notify the service to stop. We rely on the main
recipe to make sure that the service is started. This avoids multiple
restarts if both the package and the config change.
For example, we have a library module that contains a routine
that does the equivalent of 'rpm -q a name'. If the package isn't
installed yet, then the library routine will just return an empty
string and that'll be different from the post install version.
In the recipe itself, we then have the following: (This is from
our glance recipe.)
# Get access to the library routine that can look up package
# versions. Note that we're including it twice. The first time is
# so that we can get the preinstall version during the compile phase.
# The second include is so that we can check the package version
# during the run-time phase. Yes, we could have done the preinstall check
# at run time and just had one include, but that rubyblock of code is
# more complicated than doing the include.
class ::Chef::Recipe # rubocop:disable
Documentation,ClassAndModuleChildren
include our special module
end
class ::Chef # rubocop:disable ClassAndModuleChildren
class Resource
class RubyBlock # rubocop:disable Documentation
include our special module
end
end
end
...
package install commands
...
# trigger_pkg is the package that we want to check and was picked it up
# from an attribute. We'll call our library routine (this is at compile
# time) and stash the preinstall version.
node.default['openstack']['image']['preinstall'] =
pkg_version(trigger_pkg)
# Check the installed version at runtime, after the pkg commands
# have actually run. If there's a change in the version, then tell
# glance to shutdown. It'll get restarted later on and pick up the
# new binaries.
ruby_block 'glance postinstall' do
block do
postinstall_version = pkg_version(trigger_pkg)
preinstall_version = node['openstack']['image']['preinstall']
Chef::Log.info preinstall version: #{preinstall_version}
Chef::Log.info postinstall version:#{postinstall_version}
if preinstall_version != postinstall_version
Chef::Log.info 'Stopping glance services'
resources(service: 'glance-api').run_action(:stop)
resources(service: 'glance-registry').run_action(:stop)
else
Chef::Log.info 'No need to stop glance services'
end
end
end
That's the basics. Is this worth pursuing? If it seems reasonable
then I'll be happy to write up a spec, including any suggestions y'all
may have. I.e. there may be some really braindead stuff in there just
from my ignorance and flailing around just to make it work. I'm
definitely open to suggestions.
It's an interesting use case, that's for sure. I think a spec around
this, and have a chance for us to talk it out would probably be
advantageous to say the least. I see the advantage of this I really do,
but we've been taking on IRC and it seems that we're gonna try to
simplify our cookbooks for this next cycle, our cookbooks have just
become so complex that we're worried we're scaring people off.
Anyway, lets start with a spec and move from there. Thanks!
Best Regards,
JJ Asghar
c: 512.619.0722 t: @jjasghar irc: j^2
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [openstack-operators][chef] Pre-Release of knife-openstack is out (1.3.0.rc.1)
On Jun 25, 2015, at 2:58 PM, JJ Asghar jasg...@chef.io wrote: I have released the 1.3.0.rc.0 version of the knife-openstack[1] gem. I have bumped the rc.1 and pushed the gem to rubygems.org. I added the initial floating_ip ability to list the floating_ip(s) from the knife plugin. We should be able to add more features as we progress. If you would like to give it a shot you’ll need to install both knife-cloud and knife-openstack pre'd: gem install knife-cloud —pre gem install knife-openstack —pre If you find any uses or have questions don’t hesitate to email me directly or put an issue[2] in. [1]: https://rubygems.org/gems/knife-openstack https://rubygems.org/gems/knife-openstack [2]: https://github.com/chef/knife-openstack/issues https://github.com/chef/knife-openstack/issues __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [openstack-operators][chef] Pre-Release of knife-openstack is out (1.3.0.rc.0)
I have released the 1.3.0.rc.0 version of the knife-openstack[1] gem. If you find any uses or have questions don’t hesitate to email me directly or put an issue[2] in. We are planning on waiting for the floating-ip issue[3] to be resolved before the official release happens. [1]: https://rubygems.org/gems/knife-openstack https://rubygems.org/gems/knife-openstack [2]: https://github.com/chef/knife-openstack/issues https://github.com/chef/knife-openstack/issues [3]: https://github.com/chef/knife-openstack/issues/138 https://github.com/chef/knife-openstack/issues/138 -JJ__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [openstack-operators][chef] Release of knife-openstack is out (1.2.0)
I have released the 1.2.0 version of the knife-openstack[1] gem. If you find any uses or have questions don’t hesitate to email me directly or put an issue[2] in. [1]: https://rubygems.org/gems/knife-openstack https://rubygems.org/gems/knife-openstack [2]: https://github.com/chef/knife-openstack/issues https://github.com/chef/knife-openstack/issues -JJ __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [openstack-operators][openstack][chef] Pre-release of knife-openstack is out (1.2.0.rc1)
On Jun 4, 2015, at 6:12 PM, JJ Asghar jasg...@chef.io wrote: I have cut a new release of the knife-openstack[1] gem today. We have a couple new features[2] which has been asked for a while. I have pushed another pre-release (1.2.0.rc2) of knife-openstack. The main change is support for the `—bootstrap-template` now. If you would like to give it a shot and report back any issues you might find[3]. gem install knife-openstack --pre I’m hoping to give this a week or two to bake, then I’ll push it to master and a 1.2.0 release. If you have any questions, thoughts, concerns please don’t hesitate to reach out! [1]: https://rubygems.org/gems/knife-openstack https://rubygems.org/gems/knife-openstack [2]: https://github.com/chef/knife-openstack/pull/165/files https://github.com/chef/knife-openstack/pull/165/files [3]: https://github.com/chef/knife-openstack/issues https://github.com/chef/knife-openstack/issues -JJ Thanks!__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [openstack-operators][openstack][chef] Pre-release of knife-openstack is out (1.2.0.rc1)
Hey everyone! I have cut a new release of the knife-openstack[1] gem today. We have a couple new features[2] which has been asked for a while. If you would like to give it a shot and report back any issues you might find[3]. gem install knife-openstack --pre I’m hoping to give this a week or two to bake, then I’ll push it to master and a 1.2.0 release. If you have any questions, thoughts, concerns please don’t hesitate to reach out! [1]: https://rubygems.org/gems/knife-openstack https://rubygems.org/gems/knife-openstack [2]: https://github.com/chef/knife-openstack/pull/165/files https://github.com/chef/knife-openstack/pull/165/files [3]: https://github.com/chef/knife-openstack/issues https://github.com/chef/knife-openstack/issues -JJ __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [chef] OpenStack-Chef client-cookbook hacking
On Jun 1, 2015, at 12:32 PM, JJ Asghar jasg...@chef.io wrote: Please answer select the best time for you asap, and tomorrow at 1600UTC i’ll send out the time that has been decided. Ok, so it seems we’re going to have the hack session 1900UTC Wednesday. I’ll see y’all in the IRC channel! -J __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [chef] OpenStack-Chef client-cookbook hacking
Hey everyone! Per our meeting today[1] I’ve put together a doodle[2] for some time slots for us to come together and hack on the client-cookbook[3]. Please answer select the best time for you asap, and tomorrow at 1600UTC i’ll send out the time that has been decided. Thanks! -JJ [1]: https://etherpad.openstack.org/p/openstack-chef-meeting-20150601 https://etherpad.openstack.org/p/openstack-chef-meeting-20150601 [2]: http://doodle.com/gvn3v2t76czewwg6 [3]: https://github.com/stackforge/cookbook-openstack-client https://github.com/stackforge/cookbook-openstack-client__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [openstack-operators][chef] Thanks again, and we've already made amazing progress since Summit!
All, I’d like to thank everyone that came to the Vancouver Summit and our Official Ops Meeting[1]. Since then we have officially been sanctioned[2] and made amazing progress with true integration testing our cookbooks[3][4], including leveraging Rally[5] for benchmarking. Turns out after the meeting Mark, Jan, Allan, and I sat down and with some conversations with the infra team been able to push our testing without having to build a Jenkins/drone instance. Needless to say this was hugely amazing and shows what happens when we have lines of communication open and a quick feedback loop. I’m excited to see what we can make happen as a community over the next cycle(s). I thought I would drop everyone a note, say that your input has been invaluable and we are making leaps and bounds already. If you’re curious, I’ve put the review in to move from stackforge to openstack officially via infra[6] and it’s slated for next weeks infra meeting[7]. Any relevant update I’ll pass along. If you have any questions or comments, thoughts anything don’t hesitate to reach out and again, thanks again everyone! -JJ [1]: https://etherpad.openstack.org/p/YVR-ops-chef https://etherpad.openstack.org/p/YVR-ops-chef [2]: https://review.openstack.org/#/c/175000/ https://review.openstack.org/#/c/175000/ [3]: https://review.openstack.org/#/c/185085/ https://review.openstack.org/#/c/185085/ [4]: https://review.openstack.org/#/c/185178/ https://review.openstack.org/#/c/185178/ [5]: https://wiki.openstack.org/wiki/Rally https://wiki.openstack.org/wiki/Rally [6]: https://review.openstack.org/#/c/186532/ https://review.openstack.org/#/c/186532/ [7]: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [openstack-operators][chef] OpenStack+Chef is part of the big tent
Hey everyone! I’d like to just drop a note to the list saying thank you and congratulations to our general community. As of 2015-05-26 we’ve been merged into the “big tent”[1] sanctioning us as an official OpenStack project. This is amazing news, and lets keep up the great work! If you have an questions or thoughts please don’t hesitate to reach out. [1]: https://review.openstack.org/#/c/175000/ https://review.openstack.org/#/c/175000/ Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [chef] OpenStack-Chef Dev Meetup
On May 12, 2015, at 3:00 PM, JJ Asghar jasg...@chef.io wrote: I’d like to announce the OpenStack-Chef Dev Meetup in Vancouver. We have an etherpad[1] going with topics people would like to discuss. I haven’t found a room or space for us yet, but when I do I’ll comment back on this thread and add it to the etherpad. We do have a time though which is Wednesday 0950 to 1030. So please keep that in mind. As discussed in our IRC meeting on 2015-05-11 we are planning on on using most if not all of the time to plan out our last mile to getting to stable/kilo. This is an opportunity like we’ve had in the past to all share a screen and make sure we get all the major points done or discussed. Hey Everyone, so it seems I need to take a step back because I got some wires crossed. Turns out the Ops meetup is our offical meeting space during the Summit which i put on the on the etherpad[2]. I’d like to keep this on topic per the agenda we’ve created on that etherpad. I think this is best, it gives the larger community of OpenStack+Chef users to come together and discuss future plans and questions in a face to face in a real time discussion. Though this brings up the topic of the Dev meetup. As the majority of the core members are going to be at the Summit, we still need a time and a place for us to discuss the stable/kilo branching. I propose we find a working space, and just spend an hour or two together. I’ve created a doodle[3] with some time slots, if you could put your ideal time in, including your email address so we can organize off the mailing list. I’ll @core this in the IRC channel too. I’m sorry for the confusion, I made some assumptions and hopefully haven’t confused more. Please don’t hesitate to reach out to me personally with my contact info and the bottom, and I’m looking forward collaborating with you in any and all capacity next week. Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar e: j...@chef.io mailto:j...@chef.io [1]: https://etherpad.openstack.org/p/YVR-dev-chef https://etherpad.openstack.org/p/YVR-dev-chef[2]:https://etherpad.openstack.org/p/YVR-ops-chef https://etherpad.openstack.org/p/YVR-ops-chef [3]:http://doodle.com/gb4ww6izbwg8k9di http://doodle.com/gb4ww6izbwg8k9di __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [openstack-operators][chef] OpenStack-Chef Official Ops Meetup
On May 12, 2015, at 3:00 PM, JJ Asghar jasg...@chef.io wrote: I’d like to announce the OpenStack-Chef Ops Meetup in Vancouver. We have an etherpad[1] going with topics people would like to discuss. I haven’t found a room or space for us yet, but when I do I’ll comment back on this thread and add it to the etherpad, (right now looking at the other declaration of time slots, I think Wednesday 1630 is going to be our best bet) As with the Paris Ops Meetup we had a lot of great questions and use cases discussed but it was very unstructured and I got some negative feedback about that, hence the etherpad. Hey Everyone, so it seems I need to take a step back because I got some wires crossed. Turns out the Ops meetup is our offical meeting space during the Summit which i put on the on the etherpad[1]. I’d like to keep this on topic per the agenda we’ve created on that etherpad. I think this is best, it gives the larger community of OpenStack+Chef users to come together and discuss future plans and questions in a face to face in a real time discussion. Just so we have it documented in this email: the meetup is in Room 217 on Wednesday at 0950am[2]. Though this brings up the topic of the Dev meetup. As the majority of the core members are going to be at the Summit, we still need a time and a place for us to discuss the stable/kilo branching. I propose we find a working space, and just spend an hour or two together. I’ve created a doodle[3] with some time slots, if you could put your ideal time in, including your email address so we can organize off the mailing list. I’ll @core this in the IRC channel too. This is also open to the community as a whole, so if you’d like to post your ideal time don’t hesitate to. If I can ask for a volunteer note-taker to step up and to directly contact me; so when we start the meeting we can just jump in that would me amazing. I can sweeten the deal if you step up with some Chef Swag too ;). Just to follow up on this, I haven’t had anyone step up yet, so if you where thinking about it, please don’t hesitate to reach out. [1]: https://etherpad.openstack.org/p/YVR-ops-chef https://etherpad.openstack.org/p/YVR-ops-chef [2]: http://sched.co/3D8a http://sched.co/3D8a[3]: http://doodle.com/gb4ww6izbwg8k9di http://doodle.com/gb4ww6izbwg8k9di__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [chef][infra] #openstack-meeting-5 proposal to open up
On May 13, 2015, at 3:29 AM, Thierry Carrez thie...@openstack.org wrote: Can I go ahead and update the wiki to reflect this? Is there anything else i need to do procedurally to claim that hour? No, just update the wiki. Awesome, done and done, thanks so much! __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [chef][infra] #openstack-meeting-5 proposal to open up
On May 12, 2015, at 4:53 AM, Jan Klare j.kl...@x-ion.de wrote: i think you meant 16:00 UTC == 16:00 GMT == 17:00 BST for our meeting on Monday? Regarding the official meeting room: it would be great if we could get one :) Yep, you are correct. The mixture of GMT and UTC seems to have thrown me off. I’ll take an action item to convert everything to UTC so we only use UTC now to talk about things. I’ll respond to Thierry to update the time and or stake a claim in a meeting room if i can find a free one. For our second sync up meeting on Thursday to include people from Asia, zhiwei and myself agreed that 8:00 UTC would be a fitting time for Europe and Asia. The question here is if anybody else would join the meeting ? If so, please respond to this mail, else we would just drop the second meeting. I saw this initial conversation pop up on my phone last night. Unfortunately that’s 3AM my time, so the back scroll reading will be how i catch up. -JJ__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [chef][infra] #openstack-meeting-5 proposal to open up
On May 12, 2015, at 6:56 AM, Thierry Carrez thie...@openstack.org wrote: JJ Asghar wrote: We have our official meeting time at 1500UTC/1600GMTorBST on Monday and it seems all the rooms are taken. Is it possible to open up #openstack-meeting-5? I asked in #openstack-infra and fungi suggested I ask the mailing list. That said, I'd consider that OpenStack projects should have priority in the #openstack-meeting rooms. The Monday 15:00 UTC slot is blocked by two non-OpenStack project teams: Satori and Akanda. If the choice is between creating another meeting channel and asking non-OpenStack projects to move sometimes/somewhere else, I think at this time the second option makes most sense. Satori, in particular, never met once in the last 7 months. I think we can safely retire their meeting slot and give it to you (in #openstack-meeting-alt) First thanks for finding us a room. I greatly appreciate you going through the time to find us something. Unfortunately I got BST/GMT/UTC mixed up and it turns out we are looking for 1600 UTC. I’ve discovered that we have things in both UTC and GMT, and I’ve taken an action item to convert everything to UTC and only use UTC from now on. Turns out there are two open slots at 1600 UTC on Mondays. I’m requesting to take #openstack-meeting-3 as our official meeting time as of next Monday 2015-05-18. Can I go ahead and update the wiki to reflect this? Is there anything else i need to do procedurally to claim that hour? Thanks! -JJ __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [chef] 2015-05-11 Status Meeting
On May 11, 2015, at 2:36 PM, JJ Asghar jasg...@chef.io wrote: Here’s a link[1] to the status meeting for this week. Just as a reminder we are officially moving the 1600GMT time slot as of next week. I’m still in the process of finding the official channel and i’ll respond to this email when i have it. I’d like to follow up on this and make it clear it’s 1600UTC not GMT, officially we are standardizing on UTC from now on, our bot, wiki, and documentation will all be updated in due course. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [chef] OpenStack-Chef Dev Meetup
Hey Everyone! I’d like to announce the OpenStack-Chef Dev Meetup in Vancouver. We have an etherpad[1] going with topics people would like to discuss. I haven’t found a room or space for us yet, but when I do I’ll comment back on this thread and add it to the etherpad. We do have a time though which is Wednesday 0950 to 1030. So please keep that in mind. As discussed in our IRC meeting on 2015-05-11 we are planning on on using most if not all of the time to plan out our last mile to getting to stable/kilo. This is an opportunity like we’ve had in the past to all share a screen and make sure we get all the major points done or discussed. I hope to see you there and don’t hesitate to reach out if you have any relevant questions. Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar [1]: https://etherpad.openstack.org/p/YVR-dev-chef https://etherpad.openstack.org/p/YVR-dev-chef __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [chef] 2015-05-11 Status Meeting
Hey everyone! Here’s a link[1] to the status meeting for this week. Just as a reminder we are officially moving the 1600GMT time slot as of next week. I’m still in the process of finding the official channel and i’ll respond to this email when i have it. Unless there is significant objections i believe we should have our status meeting for next week also, and the agenda is posted here[2]. I understand a lot of us will be at Summit, but even with the possibility of progress on some of the outstanding action items over this next week, it would be nice to get an update. Questions, concerns, thoughts? -JJ [1]: https://etherpad.openstack.org/p/openstack-chef-meeting-20150511 https://etherpad.openstack.org/p/openstack-chef-meeting-20150511 [2]: https://etherpad.openstack.org/p/openstack-chef-meeting-20150518 https://etherpad.openstack.org/p/openstack-chef-meeting-20150518 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [chef][infra] #openstack-meeting-5 proposal to open up
Hey everyone! The openstack-chef project is attempting to move into the big tent[1]. As part of this we need to move our meeting from #openstack-chef to one of the official meeting rooms. We have our official meeting time at 1500UTC/1600GMTorBST on Monday and it seems all the rooms are taken. Is it possible to open up #openstack-meeting-5? I asked in #openstack-infra and fungi suggested I ask the mailing list. Thoughts, questions, concerns? -JJ [1]: https://review.openstack.org/#/c/175000 https://review.openstack.org/#/c/175000__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [chef] Feedback to move IRC Monday meeting and time.
On May 6, 2015, at 11:33 PM, Samuel Cassiba s...@cassiba.com wrote: This has actually caused a situation that I’d like to make public. In the documentation the times for the meetings are suggested at the top of the hour, we have ours that start at :30 past. This allows for our friends and community members on the west coast of the United States able to join at a pseudo-reasonable time. The challenge is, if we move it forward to the top of the hour, we may lose the west coast, but if we move it back to the top of the next hour we may lose our friends in Germany and earlier time zones. Moving it to the top of the hour would still fall in the realm of pseudo-reasonable, as reasonable as meetings in that timeframe can be. 0800 is more reasonable than 0730. ;-) By doing that, it would allow the group to remain as inclusive as possible, while still allowing time for commutes for us west coasters. Awesome! Yeah so it looks like we’ve gotten some positive feedback about moving the meeting to 1600GMT. We’ll discuss it and ideally make it official on Monday, and it’s already added to the agenda[1]. -JJ [1]: https://etherpad.openstack.org/p/openstack-chef-meeting-20150511 https://etherpad.openstack.org/p/openstack-chef-meeting-20150511 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [chef] Feedback to move IRC Monday meeting and time.
Hey everyone! As we move forward with our big tent move[1] Jan suggested we move from our traditional IRC meeting in our main channel #openstack-chef to one of the official OpenStack meeting channels[2]. This has actually caused a situation that I’d like to make public. In the documentation the times for the meetings are suggested at the top of the hour, we have ours that start at :30 past. This allows for our friends and community members on the west coast of the United States able to join at a pseudo-reasonable time. The challenge is, if we move it forward to the top of the hour, we may lose the west coast, but if we move it back to the top of the next hour we may lose our friends in Germany and earlier time zones. I’m not sure what to do here, so i’d like some feedback from the community. When we’ve come to a consensus we can attempt to find the open slot in the official IRC channels and i can put the stake in the ground here[3]. Thoughts, questions, concerns? -JJ [1]: https://review.openstack.org/#/c/175000/ https://review.openstack.org/#/c/175000/ [2]: https://wiki.openstack.org/wiki/Meetings/CreateaMeeting https://wiki.openstack.org/wiki/Meetings/CreateaMeeting [3]: https://wiki.openstack.org/wiki/Meetings#Chef_Cookbook_meetings https://wiki.openstack.org/wiki/Meetings#Chef_Cookbook_meetings__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [chef] A new Core Member
I’d like to announce and congratulate Samuel Cassiba as a new core member for the Openstack-Chef project. Please congratulate and thank him for stepping up! -JJ Asghar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [puppet] creating a rubygems mirror for OpenStack
On Apr 27, 2015, at 9:19 PM, Emilien Macchi emil...@redhat.com wrote: Hi, Hey! All Puppet OpenStack jobs (lint, syntax, unit and beaker) are quite often affected by rubygems.org downtimes and make all jobs failing randomly because it can't download some gems during the bootstrap. This is something that really affect our CI and we would really appreciate openstack-infra's help! Our OpenStack+Chef project is effected by this also. It came up on IRC we could use the existing Pypi mirror nodes to add rubygems and have rubygems.openstack.org or something like this). I love this idea; we are moving from bundler, to the ChefDK, but we still would benefit from having access to this. I created a story here: https://storyboard.openstack.org/#!/story/2000247 https://storyboard.openstack.org/#!/story/2000247 Thanks! I’ll keep an eye on this. Best Regards, JJ Asghar c: 512.619.0722 t: @jjasghar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [chef] Openstack-Chef has officially moved to this mailing list
Hey everyone! Per moving to the OpenStack namespace[1] the OpenStack Chef community has moved from our Google Group[2] to this mailing list. This is just a notification to the wider audience that this has happened. -JJ Asghar [1]: https://review.openstack.org/#/c/175000/ https://review.openstack.org/#/c/175000/ [2]: https://groups.google.com/forum/#!forum/opscode-chef-openstack__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [chef] Status Meeting April 20, 2015
Hey Everyone! Here’s a link to the hangout: https://plus.google.com/hangouts/_/hoaevent/AP36tYenNDpCZC-E2cbqw7050E-AG7RI8SL6bWjGMyuYGKGkCJIcpw?authuser=0hl=en https://plus.google.com/hangouts/_/hoaevent/AP36tYenNDpCZC-E2cbqw7050E-AG7RI8SL6bWjGMyuYGKGkCJIcpw?authuser=0hl=en And here’s the link to the youtube video: http://youtu.be/x5wOFwpYGqI http://youtu.be/x5wOFwpYGqI -J__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [chef] PTL Candidacy
Hey everyone! Starting the process of moving Chef into the “big tent” of OpenStack, I’d like to offer my candidacy for the PTL of the Liberty cycle. My Qualifications I have been shepherding the OpenStack Chef community since July of last year. My role at Chef is the “OpenStack guy.” I have stepped up and done my best to backfill Matt Ray and have the community move forward. Under my shepherding we have 2 weekly meetings, one Monday via Google hangouts, recorded here [1] and IRC meetings on Thursday which are recorded here [2]. My Plans for Liberty Cycle With a working testing-stack my overarching goal it so create a an automated continuous integration system that is publicly accessible and is also initially a non-voting member of our community. We have made huge leaps and bounds with the progress and I don’t want to loose the momentum. Along with the automation, I’m actively recruiting for the community and attempting to gain more people to help test and join our community. This has proven to be challenging, but it’s important for our community to grow. With the movement towards the OpenStack Big Tent this’ll require multiple parallel tasks and collaboration between multiple companies and institutions. I believe I help shepherding us through this and believe I’m up for that challenge. Thank you for your time reading this, and please don’t hesitate to reach out to me j...@chef.io mailto:j...@chef.io or on irc as j^2. -JJ Asghar [1]: https://www.youtube.com/channel/UCPQhSl-wxgWJH6_r7pk5PbQ/videos https://www.youtube.com/channel/UCPQhSl-wxgWJH6_r7pk5PbQ/videos [2]: http://eavesdrop.openstack.org/meetings/openstack_chef/ http://eavesdrop.openstack.org/meetings/openstack_chef/__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [chef] Started the review to move from stackforge to openstack
Hey Everyone! I’ve started the review [1] to move from stackforge to openstack namespace. I’m looking for comments, ideas and any pointers. Please don’t hesitate to reach out via the review, email, or IRC on freenode. Thanks! JJ Asghar (j^2) [1]: https://review.openstack.org/175000 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [chef] A new Core member!
Hey everyone! I’d like to announce that Zhiwei Chen has stepped up as a new Core Member. Please take a moment to congratulate him! Thanks Zhiwei! JJ Asghar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [chef] Naming the Project
In following the footsteps of the Puppet modules becoming a OpenStack project, the Chef cookbooks are starting the process also. I’ll be starting the review to the governance project soon, but the community needs to discuss it during our weekly hangout on Monday. One of the largest challenges in getting this project off the ground, just like Puppet, is naming the project. I have created an etherpad [1] to help capture the suggested names. I’m taking the action item to talk to the legal teams of both institutions to make sure we are all above board. If you can, please add suggestions or comment back on this thread. I’d love to see people +1 the suggestions they like too if you can spare the cycles. Thanks! JJ Asghar [1]: https://etherpad.openstack.org/p/chef-openstack-naming https://etherpad.openstack.org/p/chef-openstack-naming__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
