[openstack-dev] Move of openstack-salt project

[Filip Pytloun]

Hello,

I would like to announce migration of openstack-salt to join remaining
formulas of the ecosystem.
Since today, openstack-salt and other formulas are living at
github.com/salt-formulas.

In the past few years this ecosystem has grown to more than 90 formulas
suitable for deployment of anything from base OS, CI/CD systems, IDM up
to complex systems like Openstack, Kubernetes and more.

With this growt we believe that unifying location of all salt formulas
respecting same concepts and direction will make development and usage
simpler. Openstack formulas are only a small subset of this ecosystem so
it makes perfect sense to move them to join with the rest under one
project.

Here are links to project resources, more are going to come soon..

Github: https://github.com/salt-formulas
Launchpad https://launchpad.net/salt-formulas
IRC: #salt-formulas @ irc.freenode.net

Feel free to join and idle/discuss at IRC channel :-)

Filip


signature.asc
Description: 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] [security] [salt] Removal of Security and OpenStackSalt project teams from the Big Tent

[Filip Pytloun]

Thank you for your feedback - this is first one since we joined Big Tent
and very useful.

On 2016/09/21 17:08, Davanum Srinivas wrote:
> Data points so far are:
> 1. No response during Barcelona planning for rooms
> 2. Lack of candidates for PTL election
> 3. No activity in the releases/ repository hence no entries in
> https://releases.openstack.org/

First releases were done during project move and it seems this was
forgotten. Anyway there's new release planned to be done.

> 4. Meetings are not so regular?
> http://eavesdrop.openstack.org/meetings/openstack_salt/2016/ (supposed
> to be weekly)

There was decreased activity last few months mostly because one of
members who was leading these meetings temporarily disconnected from the
project and because there wasn't anything on agenda to discuss. Still
these meetings were taken at least 1~2x a month which seemed to be
sufficient.

> 5. Is the specs repo really active?
> http://git.openstack.org/cgit/openstack/openstack-salt-specs/ is the
> work being done elsewhere?

Very excessive documentation and other info is at separate developer
pages: http://docs.openstack.org/developer/openstack-salt/
There should be surely new record in specs after new release is made.

> 6. Is there an effort to add stuff to the CI jobs running on openstack
> infrastructure? (can't seem to find much
> http://codesearch.openstack.org/?q=salt=nope=zuul%2Flayout.yaml=project-config)

There are tests already doing mostly linting (running states in
dry-run). More complex tests are in progress but it takes some time
mostly because used technology is a little bit controversial (there's no
usable standard in saltstack community yet).

> 
> I'll stop here and switch to #openstack-salt channel to help work you
> all through if there is a consensus/willingness from the
> openstack-salt team that there's significant work to be done. If you
> think you are better off not on the governance, that would be your
> call as well.

I think we are going to fix things, to summarize:

 - make new release for Newton + update specs
 - elect new PTL
 - be more active in openstack-dev mailing list (maybe also have
   separate ML just for our team?)

If there's more we can do, we are available at Freenode/#openstack-salt.

-- 
Filip Pytloun
Cloud Architect
 
[tcp ◕ cloud]
 
tcp cloud a.s.
Thamova 16, 180 00  Prague 8
 
Mobile: +420 776 004 323
E-mail: filip.pytl...@tcpcloud.eu
GPG:3802 93B1 6CA8 C7A0 695B  8B28 6808 239B 9C72 E61B
Web:http://www.opentcpcloud.org/


signature.asc
Description: Digital 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] [security] [salt] Removal of Security and OpenStackSalt project teams from the Big Tent

[Filip Pytloun]

really soon now to go in that
> > > >> direction.
> > > >> 
> > > >> In the UX case, the current PTL (Piet Kruithof) very quickly reacted,
> > > >> explained his error and asked to be considered for the position for
> > > >> Ocata. The TC will officialize his nomination at the next meeting,
> > > >> together with the newly elected PTLs.
> > > >> 
> > > >> That leaves us with OpenStackSalt and Security, where nobody reacted to
> > > >> the announcement that we are missing PTL candidates. That points to a
> > > >> real disconnect between those teams and the rest of the community. Even
> > > >> if you didn't have the election schedule in mind, it was pretty hard to
> > > >> miss all the PTL nominations in the email last week.
> > > >> 
> > > >> The majority of TC members present at the meeting yesterday suggested
> > > >> that those project teams should be removed from the Big Tent, with 
> > > >> their
> > > >> design summit space allocation slightly reduced to match that (and make
> > > >> room for other not-yet-official teams).
> > > >> 
> > > >> In the case of OpenStackSalt, it's a relatively new addition, and if
> > > >> they get their act together they could probably be re-proposed in the
> > > >> future. In the case of Security, it points to a more significant
> > > >> disconnect (since it's not the first time the PTL misses the nomination
> > > >> call). We definitely still need to care about Security (and we also 
> > > >> need
> > > >> a home for the Vulnerability Management team), but I think the 
> > > >> "Security
> > > >> team" acts more like a workgroup than as an official project team, as
> > > >> evidenced by the fact that nobody in that team reacted to the lack of
> > > >> PTL nomination, or the announcement that the team missed the bus.
> > > >> 
> > > >> The suggested way forward there would be to remove the "Security 
> > > >> project
> > > >> team", have the Vulnerability Management Team file to be its own
> > > >> official project team (in the same vein as the stable maintenance 
> > > >> team),
> > > >> and have Security be just a workgroup rather than a project team.
> > > >> 
> > > >> Thoughts, comments ?
> > > >> 
> > > >> [1]
> > > >> http://lists.openstack.org/pipermail/openstack-dev/2016-
> > > >> September/103904.html
> > > >> [2]
> > > >> http://lists.openstack.org/pipermail/openstack-dev/2016-
> > > >> September/103939.html
> > > >> 
> > > >> --
> > > >> Thierry Carrez (ttx)
> > > >> 
> > > >> __
> > > >> 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 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 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 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

-- 
Filip Pytloun
Cloud Architect
 
[tcp ◕ cloud]
 
tcp cloud a.s.
Thamova 16, 180 00  Prague 8
 
Mobile: +420 776 004 323
E-mail: filip.pytl...@tcpcloud.eu
GPG:3802 93B1 6CA8 C7A0 695B  8B28 6808 239B 9C72 E61B
Web:http://www.opentcpcloud.org/


signature.asc
Description: Digital 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] [security] [salt] Removal of Security and OpenStackSalt project teams from the Big Tent

[Filip Pytloun]

t; team", have the Vulnerability Management Team file to be its own
> >> official project team (in the same vein as the stable maintenance team),
> >> and have Security be just a workgroup rather than a project team.
> >> 
> >> Thoughts, comments ?
> >> 
> >> [1]
> >> http://lists.openstack.org/pipermail/openstack-dev/2016-
> >> September/103904.html
> >> [2]
> >> http://lists.openstack.org/pipermail/openstack-dev/2016-
> >> September/103939.html
> >> 
> >> --
> >> Thierry Carrez (ttx)
> >> 
> >> __
> >> 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 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 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


-- 
Filip Pytloun
Cloud Architect
 
[tcp ◕ cloud]
 
tcp cloud a.s.
Thamova 16, 180 00  Prague 8
 
Mobile: +420 776 004 323
E-mail: filip.pytl...@tcpcloud.eu
GPG:3802 93B1 6CA8 C7A0 695B  8B28 6808 239B 9C72 E61B
Web:http://www.opentcpcloud.org/


signature.asc
Description: Digital 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] [security] [salt] Removal of Security and OpenStackSalt project teams from the Big Tent

[Filip Pytloun]

Hello,

it's definately our bad that we missed elections in OpenStackSalt
project. Reason is similar to Rob's - we are active on different
channels (mostly IRC as we keep regular meetings) and don't used to
reading mailing lists with lots of generic topics (it would be good to
have separate mailing list for such calls and critical topics or
individual mails to project's core members).

Our project is very active [1], trying to do things the Openstack way
and I think it would be a pitty to remove it from Big Tent just because
we missed mail and therefore our first PTL election.

Of course I don't want to excuse our fault. In case it's not too late,
we will try to be more active in mailing lists like openstack-dev and
not miss such important events next time.

[1] http://stackalytics.com/?module=openstacksalt-group

-Filip

On Wed, Sep 21, 2016 at 12:23 PM, Thierry Carrez 
wrote:

> Hi everyone,
>
> As announced previously[1][2], there were no PTL candidates within the
> election deadline for a number of official OpenStack project teams:
> Astara, UX, OpenStackSalt and Security.
>
> In the Astara case, the current team working on it would like to abandon
> the project (and let it be available for any new team who wishes to take
> it away). A change should be proposed really soon now to go in that
> direction.
>
> In the UX case, the current PTL (Piet Kruithof) very quickly reacted,
> explained his error and asked to be considered for the position for
> Ocata. The TC will officialize his nomination at the next meeting,
> together with the newly elected PTLs.
>
> That leaves us with OpenStackSalt and Security, where nobody reacted to
> the announcement that we are missing PTL candidates. That points to a
> real disconnect between those teams and the rest of the community. Even
> if you didn't have the election schedule in mind, it was pretty hard to
> miss all the PTL nominations in the email last week.
>
> The majority of TC members present at the meeting yesterday suggested
> that those project teams should be removed from the Big Tent, with their
> design summit space allocation slightly reduced to match that (and make
> room for other not-yet-official teams).
>
> In the case of OpenStackSalt, it's a relatively new addition, and if
> they get their act together they could probably be re-proposed in the
> future. In the case of Security, it points to a more significant
> disconnect (since it's not the first time the PTL misses the nomination
> call). We definitely still need to care about Security (and we also need
> a home for the Vulnerability Management team), but I think the "Security
> team" acts more like a workgroup than as an official project team, as
> evidenced by the fact that nobody in that team reacted to the lack of
> PTL nomination, or the announcement that the team missed the bus.
>
> The suggested way forward there would be to remove the "Security project
> team", have the Vulnerability Management Team file to be its own
> official project team (in the same vein as the stable maintenance team),
> and have Security be just a workgroup rather than a project team.
>
> Thoughts, comments ?
>
> [1]
> http://lists.openstack.org/pipermail/openstack-dev/2016-
> September/103904.html
> [2]
> http://lists.openstack.org/pipermail/openstack-dev/2016-
> September/103939.html
>
> --
> Thierry Carrez (ttx)
>
> __
> 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
>


signature.asc
Description: Digital 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