Re: [openstack-dev] [packaging] asks from the ops meetup

2015-08-20 Thread Matthew Thode
On 08/20/2015 09:22 AM, Ian Cordasco wrote:
 
 
 On 8/19/15, 19:31, Matthew Thode prometheanf...@gentoo.org wrote:
 
 On 08/19/2015 07:22 PM, Ian Cordasco wrote:
 Questions in-line, but I'd appreciate a better summary

 On 8/19/15, 17:50, Matthew Thode prometheanf...@gentoo.org wrote:

 I'll start by giving this out, but I'll also summarize the asks we had
 from upstream.

 https://etherpad.openstack.org/p/PAO-ops-packaging


 General services:
  - gate check on example config and doc generation
- was mentioned this has broken in the past and taken a while to fix

 The etherpad doesn't have much on this topic, could you (or someone else
 from the mid-cycle) expound on this?

 Not sure, wasn't the one that brought it up, but a specific check on
 config/doc generation did seem like a good idea.
 
 A specific check on config/doc generation is ironically vague here. What
 kind of check? That they can be generated? That the generated configs are
 properly read/parsed by the project? What is it that is being asked here?
 

that they can be generated



  - document dependencies needed for config/doc generation
- (not all of test requirements)

 So you want a doc-requirements.txt file? That doesn't have other
 libraries
 other than the documentation related ones?


 Yes, though I think this may cover example config generation as well.

  - generated example configs generated and stored in an automated way
- (in lieu of packagers generating the configs dynamically)

 Don't most projects already do this?

 iirc neutron at least does not
 
 I don't think you (as operators) should be afraid to say These projects
 are not doing this. Here are the bugs that haven't been answered in
 several (days|weeks|months), please address them.
 

fair enough, I'll see about gathering / making some bugs


  - A place to look for files that go in /etc

 Again, don't most projects have an etc/ directory inside of them?

 yes, though files have been removed in favor of dynamic generation.  The
 more specific ask was for this to be auto generated and updated, which
 we don't see as being done (could be wrong)
 
 I know Glance keeps theirs up-to-date even if they don't auto-generate
 them. I'm also confident that at least Keystone auto-generates them
 periodically and commits them to the tree. I haven't checked other
 projects recently.
 

yes, this needs proper enumeration, but I would also hope that the
projects could be more standard about how they do this


  - Publish pip-freeze at the end

 At the end of what?

 of a test/gerrit run
 
 Then this already happens.

neat

 

  - Don't strip out files in the repo when publishing to pip

 No services are published to PyPI. What is this about?

 Think this is more the bash autocomplete stuff
 
 So then this isn't about Services then (despite being under the Services
 section of the summary). So the client libraries don't have their
 setup.cfg's properly configured to include bash completion files. That's a
 fair complaint. That said, bandit recently did the right thing and we
 received a bug report (via IRC) from the gentoo packaging team that we
 were doing it wrong.
 

yes, haven't seen an update for that, will need to bug you tomorrow
about it :D


  - Publish an example init-script (systemd)

 This seems reasonable

- I think this might be going away with wsgi

 What?

 the init scripts may be going away because of wsgi, it's be in apache or
 nginx or whatever


 Docs:
  - nginx wsgi examples

 Is nginx even supported in any of the services? If so, are we already
 gating on that?

 The docs give example configs for apache mod_wsgi, this was an ask for
 similiar with nginx.
 
 You fail to understand my point. Services that provide example configs for
 apache with mod_wsgi are choosing to explicitly support those
 configurations. Providing example configurations for nginx would imply a
 similar level of support from the teams documenting that. We would need to
 add gating to make sure the services behave well with nginx then as well.
 We could do this, but it isn't as simple as adding a documentation
 example.
 

ok

-- 
Matthew Thode (prometheanfire)



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


[openstack-dev] [packaging] asks from the ops meetup

2015-08-19 Thread Matthew Thode
I'll start by giving this out, but I'll also summarize the asks we had
from upstream.

https://etherpad.openstack.org/p/PAO-ops-packaging


General services:
  - gate check on example config and doc generation
- was mentioned this has broken in the past and taken a while to fix
  - document dependencies needed for config/doc generation
- (not all of test requirements)
  - generated example configs generated and stored in an automated way
- (in lieu of packagers generating the configs dynamically)
  - A place to look for files that go in /etc
  - Publish pip-freeze at the end
  - Don't strip out files in the repo when publishing to pip
  - Publish an example init-script (systemd)
- I think this might be going away with wsgi

Docs:
  - nginx wsgi examples

-- 
Matthew Thode (prometheanfire)



signature.asc
Description: OpenPGP 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] [packaging] asks from the ops meetup

2015-08-19 Thread Ian Cordasco
Questions in-line, but I'd appreciate a better summary

On 8/19/15, 17:50, Matthew Thode prometheanf...@gentoo.org wrote:

I'll start by giving this out, but I'll also summarize the asks we had
from upstream.

https://etherpad.openstack.org/p/PAO-ops-packaging


General services:
  - gate check on example config and doc generation
- was mentioned this has broken in the past and taken a while to fix

The etherpad doesn't have much on this topic, could you (or someone else
from the mid-cycle) expound on this?

  - document dependencies needed for config/doc generation
- (not all of test requirements)

So you want a doc-requirements.txt file? That doesn't have other libraries
other than the documentation related ones?

  - generated example configs generated and stored in an automated way
- (in lieu of packagers generating the configs dynamically)

Don't most projects already do this?

  - A place to look for files that go in /etc

Again, don't most projects have an etc/ directory inside of them?

  - Publish pip-freeze at the end

At the end of what?

  - Don't strip out files in the repo when publishing to pip

No services are published to PyPI. What is this about?

  - Publish an example init-script (systemd)

This seems reasonable

- I think this might be going away with wsgi

What?

Docs:
  - nginx wsgi examples

Is nginx even supported in any of the services? If so, are we already
gating on that?

__
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] [packaging] asks from the ops meetup

2015-08-19 Thread Matthew Thode
On 08/19/2015 07:22 PM, Ian Cordasco wrote:
 Questions in-line, but I'd appreciate a better summary
 
 On 8/19/15, 17:50, Matthew Thode prometheanf...@gentoo.org wrote:
 
 I'll start by giving this out, but I'll also summarize the asks we had
from upstream.

 https://etherpad.openstack.org/p/PAO-ops-packaging


 General services:
  - gate check on example config and doc generation
- was mentioned this has broken in the past and taken a while to fix
 
 The etherpad doesn't have much on this topic, could you (or someone else
 from the mid-cycle) expound on this?

Not sure, wasn't the one that brought it up, but a specific check on
config/doc generation did seem like a good idea.

 
  - document dependencies needed for config/doc generation
- (not all of test requirements)
 
 So you want a doc-requirements.txt file? That doesn't have other libraries
 other than the documentation related ones?
 

Yes, though I think this may cover example config generation as well.

  - generated example configs generated and stored in an automated way
- (in lieu of packagers generating the configs dynamically)
 
 Don't most projects already do this?

iirc neutron at least does not

 
  - A place to look for files that go in /etc
 
 Again, don't most projects have an etc/ directory inside of them?

yes, though files have been removed in favor of dynamic generation.  The
more specific ask was for this to be auto generated and updated, which
we don't see as being done (could be wrong)

 
  - Publish pip-freeze at the end
 
 At the end of what?

of a test/gerrit run

 
  - Don't strip out files in the repo when publishing to pip
 
 No services are published to PyPI. What is this about?

Think this is more the bash autocomplete stuff

 
  - Publish an example init-script (systemd)
 
 This seems reasonable
 
- I think this might be going away with wsgi
 
 What?

the init scripts may be going away because of wsgi, it's be in apache or
nginx or whatever

 
 Docs:
  - nginx wsgi examples
 
 Is nginx even supported in any of the services? If so, are we already
 gating on that?
 
The docs give example configs for apache mod_wsgi, this was an ask for
similiar with nginx.

-- 
-- Matthew Thode (prometheanfire)



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