Topics

Request Creation Review for puppet-fdio


Feng Pan <fpan@...>
 

Please accept this project proposal for puppet-fdio for consideration.

Thanks,
Feng


Joel Halpern
 

I have noted this on the TSC Page for 3-Nov, as that is the first TSC call after the two week window.

Thank you for doing this.  It seems to me that we can use improvements in deployability of fd.io.

 

Yours,

Joel

 

From: tsc-bounces@... [mailto:tsc-bounces@...] On Behalf Of Feng Pan
Sent: Wednesday, October 12, 2016 11:11 AM
To: tsc@...
Subject: [tsc] Request Creation Review for puppet-fdio

 

Please accept this project proposal for puppet-fdio for consideration.

 

Thanks,

Feng

 


Edward Warnicke
 

Feng,
      Typically repo names are: lower case, short, and suitable for use as a C identifier.  Would it be possible to choose a reponame that does not contain a '-' ?

Ed


On Wed, Oct 12, 2016 at 8:10 AM, Feng Pan <fpan@...> wrote:
Please accept this project proposal for puppet-fdio for consideration.

Thanks,
Feng


_______________________________________________
tsc mailing list
tsc@...
https://lists.fd.io/mailman/listinfo/tsc


Feng Pan <fpan@...>
 

Sure. So one of the thoughts I actually had about this project is to make it a bit broader than puppet, where we can maybe support other deployment/configuration tools as well, like ansible. If we can group those into a single project, we could call it configuration, or deployment, and within it we could have sub modules like puppet-fdio and ansible-fdio, etc. Would that make sense? 

If it's preferred that those to be separated, we could simply call this project puppet.

Thanks
Feng

On Fri, Oct 28, 2016 at 1:39 PM, Edward Warnicke <hagbard@...> wrote:
Feng,
      Typically repo names are: lower case, short, and suitable for use as a C identifier.  Would it be possible to choose a reponame that does not contain a '-' ?

Ed


On Wed, Oct 12, 2016 at 8:10 AM, Feng Pan <fpan@...> wrote:
Please accept this project proposal for puppet-fdio for consideration.

Thanks,
Feng


_______________________________________________
tsc mailing list
tsc@...
https://lists.fd.io/mailman/listinfo/tsc



Andrew Grimberg
 

Just from the point of view of someone who develops a lot of puppet
modules. Puppet modules require their own dedicated repository because
of the layout and tooling. It can't be a sub-directory. Doing anything
other than that will cause a lot of problems for any sort of automated
testing as well as any eventual release to Puppet Forge.

Doing something like the following would work:

depconf/puppet-fdio

This is a fairly standard community naming with the
puppet-<real_module_name> it's just namespacing it so it can easily
coexist with other deployment / configuration modules.

Also, as an aside, don't ever name your project just 'puppet' that's
going to cause you a world of different types of hurt.

-Andy-

On 10/28/2016 10:48 AM, Feng Pan wrote:
Sure. So one of the thoughts I actually had about this project is to
make it a bit broader than puppet, where we can maybe support other
deployment/configuration tools as well, like ansible. If we can group
those into a single project, we could call it configuration, or
deployment, and within it we could have sub modules like puppet-fdio and
ansible-fdio, etc. Would that make sense?

If it's preferred that those to be separated, we could simply call this
project puppet.

Thanks
Feng

On Fri, Oct 28, 2016 at 1:39 PM, Edward Warnicke <hagbard@...
<mailto:hagbard@...>> wrote:

Feng,
Typically repo names are: lower case, short, and suitable for
use as a C identifier. Would it be possible to choose a reponame
that does not contain a '-' ?

Ed


On Wed, Oct 12, 2016 at 8:10 AM, Feng Pan <fpan@...
<mailto:fpan@...>> wrote:

Please accept this project proposal for puppet-fdio for
consideration.
https://wiki.fd.io/view/Project_Proposals/puppet-fdio
<https://wiki.fd.io/view/Project_Proposals/puppet-fdio>

Thanks,
Feng


_______________________________________________
tsc mailing list
tsc@... <mailto:tsc@...>
https://lists.fd.io/mailman/listinfo/tsc
<https://lists.fd.io/mailman/listinfo/tsc>





_______________________________________________
tsc mailing list
tsc@...
https://lists.fd.io/mailman/listinfo/tsc
--
Andrew J Grimberg
Systems Administrator
Release Engineering Team Lead
The Linux Foundation


Feng Pan <fpan@...>
 

Hey Andy,

Yeah I realized that was a bad idea after sending my response, we should keep this repo to just be the puppet module. For the naming, Ed's comment was that they would prefer not to include '-' in the repo name, so wouldn't something like depconf/puppet-fdio also be problematic? I personally would prefer to keep it puppet-fdio to be consistent with other puppet modules in Openstack.

Thanks,
Feng

On Mon, Oct 31, 2016 at 10:07 AM, Andrew Grimberg <agrimberg@...> wrote:
Just from the point of view of someone who develops a lot of puppet
modules. Puppet modules require their own dedicated repository because
of the layout and tooling. It can't be a sub-directory. Doing anything
other than that will cause a lot of problems for any sort of automated
testing as well as any eventual release to Puppet Forge.

Doing something like the following would work:

depconf/puppet-fdio

This is a fairly standard community naming with the
puppet-<real_module_name> it's just namespacing it so it can easily
coexist with other deployment / configuration modules.

Also, as an aside, don't ever name your project just 'puppet' that's
going to cause you a world of different types of hurt.

-Andy-

On 10/28/2016 10:48 AM, Feng Pan wrote:
> Sure. So one of the thoughts I actually had about this project is to
> make it a bit broader than puppet, where we can maybe support other
> deployment/configuration tools as well, like ansible. If we can group
> those into a single project, we could call it configuration, or
> deployment, and within it we could have sub modules like puppet-fdio and
> ansible-fdio, etc. Would that make sense?
>
> If it's preferred that those to be separated, we could simply call this
> project puppet.
>
> Thanks
> Feng
>
> On Fri, Oct 28, 2016 at 1:39 PM, Edward Warnicke <hagbard@...
> <mailto:hagbard@...>> wrote:
>
>     Feng,
>           Typically repo names are: lower case, short, and suitable for
>     use as a C identifier.  Would it be possible to choose a reponame
>     that does not contain a '-' ?
>
>     Ed
>
>
>     On Wed, Oct 12, 2016 at 8:10 AM, Feng Pan <fpan@...
>     <mailto:fpan@...>> wrote:
>
>         Please accept this project proposal for puppet-fdio for
>         consideration.
>         https://wiki.fd.io/view/Project_Proposals/puppet-fdio
>         <https://wiki.fd.io/view/Project_Proposals/puppet-fdio>
>
>         Thanks,
>         Feng
>
>
>         _______________________________________________
>         tsc mailing list
>         tsc@... <mailto:tsc@...>
>         https://lists.fd.io/mailman/listinfo/tsc
>         <https://lists.fd.io/mailman/listinfo/tsc>
>
>
>
>
>
> _______________________________________________
> tsc mailing list
> tsc@...
> https://lists.fd.io/mailman/listinfo/tsc
>

--
Andrew J Grimberg
Systems Administrator
Release Engineering Team Lead
The Linux Foundation



Andrew Grimberg
 

puppet-fdio would be the puppet wide _community_ naming convention
actually. Not just OpenStack. Go look at Puppet Forge and follow the
project URL for any of the well rated, highly downloaded modules. You'll
find that they're nearly all named puppet-$modulename for their repo.

The alternative in our infra would be something like:

depconf/puppet/fdio (notice the directory hierarchy)

That being said, I understand Ed's suggestion but given that puppet-$foo
is a Puppet repository naming convention used in Puppet community as a
whole, this is one of those times I would think that it actually makes
sense to have the '-' in the repo name.

-Andy-

On 10/31/2016 07:44 AM, Feng Pan wrote:
Hey Andy,

Yeah I realized that was a bad idea after sending my response, we should
keep this repo to just be the puppet module. For the naming, Ed's
comment was that they would prefer not to include '-' in the repo name,
so wouldn't something like depconf/puppet-fdio also be problematic? I
personally would prefer to keep it puppet-fdio to be consistent with
other puppet modules in Openstack.

Thanks,
Feng

On Mon, Oct 31, 2016 at 10:07 AM, Andrew Grimberg
<@tykeal <mailto:@tykeal>>
wrote:

Just from the point of view of someone who develops a lot of puppet
modules. Puppet modules require their own dedicated repository because
of the layout and tooling. It can't be a sub-directory. Doing anything
other than that will cause a lot of problems for any sort of automated
testing as well as any eventual release to Puppet Forge.

Doing something like the following would work:

depconf/puppet-fdio

This is a fairly standard community naming with the
puppet-<real_module_name> it's just namespacing it so it can easily
coexist with other deployment / configuration modules.

Also, as an aside, don't ever name your project just 'puppet' that's
going to cause you a world of different types of hurt.

-Andy-

On 10/28/2016 10:48 AM, Feng Pan wrote:
> Sure. So one of the thoughts I actually had about this project is to
> make it a bit broader than puppet, where we can maybe support other
> deployment/configuration tools as well, like ansible. If we can group
> those into a single project, we could call it configuration, or
> deployment, and within it we could have sub modules like puppet-fdio and
> ansible-fdio, etc. Would that make sense?
>
> If it's preferred that those to be separated, we could simply call this
> project puppet.
>
> Thanks
> Feng
>
> On Fri, Oct 28, 2016 at 1:39 PM, Edward Warnicke <hagbard@... <mailto:hagbard@...>
> <mailto:hagbard@... <mailto:hagbard@...>>> wrote:
>
> Feng,
> Typically repo names are: lower case, short, and suitable for
> use as a C identifier. Would it be possible to choose a reponame
> that does not contain a '-' ?
>
> Ed
>
>
> On Wed, Oct 12, 2016 at 8:10 AM, Feng Pan <fpan@... <mailto:fpan@...>
> <mailto:fpan@... <mailto:fpan@...>>> wrote:
>
> Please accept this project proposal for puppet-fdio for
> consideration.
> https://wiki.fd.io/view/Project_Proposals/puppet-fdio
<https://wiki.fd.io/view/Project_Proposals/puppet-fdio>
> <https://wiki.fd.io/view/Project_Proposals/puppet-fdio
<https://wiki.fd.io/view/Project_Proposals/puppet-fdio>>
>
> Thanks,
> Feng
>
>
> _______________________________________________
> tsc mailing list
> tsc@... <mailto:tsc@...>
<mailto:tsc@... <mailto:tsc@...>>
> https://lists.fd.io/mailman/listinfo/tsc
<https://lists.fd.io/mailman/listinfo/tsc>
> <https://lists.fd.io/mailman/listinfo/tsc
<https://lists.fd.io/mailman/listinfo/tsc>>
>
>
>
>
>
> _______________________________________________
> tsc mailing list
> tsc@... <mailto:tsc@...>
> https://lists.fd.io/mailman/listinfo/tsc
<https://lists.fd.io/mailman/listinfo/tsc>
>

--
Andrew J Grimberg
Systems Administrator
Release Engineering Team Lead
The Linux Foundation

--
Andrew J Grimberg
Systems Administrator
Release Engineering Team Lead
The Linux Foundation