Agree.
Install guide is just a start/example, concentrate is better than cover
all, for more services we can just provide a good place to let them
discoverable, and lfor arger scale, we should use advanced tools such as
puppet and ansible
On Mon, Apr 4, 2016 at 6:12 PM, Thierry Carrez
Hi Jonathan,
It's all good, this is actually unrelated to the larger changes proposed for
Newton, but more about a late change that was proposed for Kilo.
HTH,
L
On 14/04/16 03:59, Jonathan D. Proulx wrote:
> On Wed, Apr 13, 2016 at 01:52:38PM -0400, Jonathan D. Proulx wrote:
>
> :I've not
t;; Mike
> Perez <m...@openstack.org>; openstack-d...@lists.openstack.org
> Subject: Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore
> - What about big tent?
>
> On 04/13/2016 07:17 PM, Amrith Kumar wrote:
> > Andreas, Lana, Mike, Matt, and others who
On Wed, Apr 13, 2016 at 01:52:38PM -0400, Jonathan D. Proulx wrote:
:I've not been following this thread at all so appologies if I'm
:confused.
reading follow up emails relating to timing of various submissions, I
back away slowly clearly not having all the context on this one.
-Jon
; From: Andreas Jaeger [mailto:a...@suse.com]
:> Sent: Monday, April 04, 2016 2:42 PM
:> To: OpenStack Development Mailing List (not for usage questions)
:> <openstack-dev@lists.openstack.org>
:> Subject: Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore
:> - What abou
velopment Mailing List (not for usage questions)
>> <openstack-dev@lists.openstack.org>
>> Subject: Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore
>> - What about big tent?
>>
>> On 04/04/2016 12:12 PM, Thierry Carrez wrote:
>>&g
penstack-dev] [docs] Our Install Guides Only Cover Defcore
> - What about big tent?
>
> On 04/04/2016 12:12 PM, Thierry Carrez wrote:
> > Doug Hellmann wrote:
> >>> [...]
> >>> We would love to add all sufficiently mature projects to the
> >>> install
On Mon, Apr 4, 2016 at 1:41 PM, Andreas Jaeger wrote:
> On 04/04/2016 12:12 PM, Thierry Carrez wrote:
> > Doug Hellmann wrote:
> >>> [...]
> >>> We would love to add all sufficiently mature projects to the
> >>> installation
> >>> guide because it increases visibility and adoption
On 04/04/2016 12:12 PM, Thierry Carrez wrote:
> Doug Hellmann wrote:
>>> [...]
>>> We would love to add all sufficiently mature projects to the
>>> installation
>>> guide because it increases visibility and adoption by operators, but we
>>> lack resources to develop a source installation mechanism
Doug Hellmann wrote:
[...]
We would love to add all sufficiently mature projects to the installation
guide because it increases visibility and adoption by operators, but we
lack resources to develop a source installation mechanism that retains as
much simplicity as possible for our audience.
I
Excerpts from Matt Kassawara's message of 2016-04-01 12:38:02 -0600:
> Hi,
>
> I didn't see this e-mail until now because I'm busy trying to update and
> test the installation guide in time for the Mitaka release. As a primary
> contributor to the installation guide for about six releases
Hi,
I didn't see this e-mail until now because I'm busy trying to update and
test the installation guide in time for the Mitaka release. As a primary
contributor to the installation guide for about six releases including
restructuring it a couple of times, I think I can explain why we do what we
On Wed, Mar 30, 2016, at 03:37 AM, Thomas Goirand wrote:
> On 03/29/2016 08:33 PM, Doug Hellmann wrote:
> > If the core doc team isn't able to help you maintain it, maybe it's a
> > candidate for a separate guide, just like we're discussing for projects
> > that aren't part of the DefCore set
On 03/29/2016 08:33 PM, Doug Hellmann wrote:
> If the core doc team isn't able to help you maintain it, maybe it's a
> candidate for a separate guide, just like we're discussing for projects
> that aren't part of the DefCore set included in the main guide.
>
> Doug
This is exactly what I don't
Excerpts from Thomas Goirand's message of 2016-03-29 13:37:14 +0200:
> On 03/29/2016 11:56 AM, Neil Jerram wrote:
> > On 29/03/16 09:38, Thomas Goirand wrote:
> >> On 03/23/2016 04:06 PM, Mike Perez wrote:
> >>> Hey all,
> >>>
> >>> I've been talking to a variety of projects about lack of install
On 29/03/16 12:40, Thomas Goirand wrote:
>
> The documentation people decided to *not* publish the Debian
> install-guide (and remove the link to it) even though it can be
> generated and (to my opinion, which is probably biased) works well.
>
> I'd like to know the steps needed to restore a
On 03/29/2016 11:56 AM, Neil Jerram wrote:
> On 29/03/16 09:38, Thomas Goirand wrote:
>> On 03/23/2016 04:06 PM, Mike Perez wrote:
>>> Hey all,
>>>
>>> I've been talking to a variety of projects about lack of install guides.
>>> This
>>> came from me not having a great experience with trying out
On 29/03/16 09:38, Thomas Goirand wrote:
> On 03/23/2016 04:06 PM, Mike Perez wrote:
>> Hey all,
>>
>> I've been talking to a variety of projects about lack of install guides. This
>> came from me not having a great experience with trying out projects in the
>> big
>> tent.
>>
>> [...]
>
> Sorry
On 03/23/2016 04:06 PM, Mike Perez wrote:
> Hey all,
>
> I've been talking to a variety of projects about lack of install guides. This
> came from me not having a great experience with trying out projects in the big
> tent.
>
> [...]
Sorry to jump in this conversation a bit later, as I missed
The only downside I see of these examples are there is no way in the
documentation to determine the release version or cycle. (i.e. you have to
read the contents in conjunction with the URL).
Ronald Bradford
Web Site: http://ronaldbradford.com
LinkedIn:
On Fri, Mar 25, 2016 at 03:20:30PM -0400, Doug Hellmann wrote:
> Excerpts from Jim Rollenhagen's message of 2016-03-25 10:45:30 -0700:
> > On Fri, Mar 25, 2016 at 09:10:05AM -0400, Doug Hellmann wrote:
> > > Excerpts from Lana Brindley's message of 2016-03-24 08:50:49 +1000:
> > > > On 24/03/16
Excerpts from Andreas Jaeger's message of 2016-03-25 20:30:01 +0100:
> On 03/25/2016 08:20 PM, Doug Hellmann wrote:
> > Excerpts from Jim Rollenhagen's message of 2016-03-25 10:45:30 -0700:
> >> > On Fri, Mar 25, 2016 at 09:10:05AM -0400, Doug Hellmann wrote:
> >>> > > Excerpts from Lana
On 03/25/2016 08:20 PM, Doug Hellmann wrote:
> Excerpts from Jim Rollenhagen's message of 2016-03-25 10:45:30 -0700:
>> > On Fri, Mar 25, 2016 at 09:10:05AM -0400, Doug Hellmann wrote:
>>> > > Excerpts from Lana Brindley's message of 2016-03-24 08:50:49 +1000:
> > > On 24/03/16 08:01, Doug
Excerpts from Jim Rollenhagen's message of 2016-03-25 10:45:30 -0700:
> On Fri, Mar 25, 2016 at 09:10:05AM -0400, Doug Hellmann wrote:
> > Excerpts from Lana Brindley's message of 2016-03-24 08:50:49 +1000:
> > > On 24/03/16 08:01, Doug Hellmann wrote:
> > > > Excerpts from Lana Brindley's message
Excerpts from Mike Perez's message of 2016-03-25 11:32:58 -0700:
> > On Mar 25, 2016, at 06:10, Doug Hellmann wrote:
> >
> > Excerpts from Lana Brindley's message of 2016-03-24 08:50:49 +1000:
> >>
> >> All docs need to be drafted somewhere. I don't care where that is,
On Fri, Mar 25, 2016 at 11:32:58AM -0700, Mike Perez wrote:
> > On Mar 25, 2016, at 06:10, Doug Hellmann wrote:
> >
> > Excerpts from Lana Brindley's message of 2016-03-24 08:50:49 +1000:
> >>
> >> All docs need to be drafted somewhere. I don't care where that is, but
>
> On Mar 25, 2016, at 06:10, Doug Hellmann wrote:
>
> Excerpts from Lana Brindley's message of 2016-03-24 08:50:49 +1000:
>>
>> All docs need to be drafted somewhere. I don't care where that is, but make
>> the suggestion of /developer because at least it's accessible
On Fri, Mar 25, 2016 at 09:10:05AM -0400, Doug Hellmann wrote:
> Excerpts from Lana Brindley's message of 2016-03-24 08:50:49 +1000:
> > On 24/03/16 08:01, Doug Hellmann wrote:
> > > Excerpts from Lana Brindley's message of 2016-03-24 07:14:35 +1000:
> > >> Hi Mike, and sorry I missed you on IRC
Excerpts from Lana Brindley's message of 2016-03-24 08:50:49 +1000:
> On 24/03/16 08:01, Doug Hellmann wrote:
> > Excerpts from Lana Brindley's message of 2016-03-24 07:14:35 +1000:
> >> Hi Mike, and sorry I missed you on IRC to discuss this there. That said, I
> >> think it's great that you took
On Wed, Mar 23, 2016 at 06:02:47PM -0400, Doug Hellmann wrote:
> Excerpts from Jim Rollenhagen's message of 2016-03-23 14:46:16 -0700:
> > On Thu, Mar 24, 2016 at 07:14:35AM +1000, Lana Brindley wrote:
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA256
> > >
> > > Hi Mike, and sorry I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 24/03/16 08:01, Doug Hellmann wrote:
> Excerpts from Lana Brindley's message of 2016-03-24 07:14:35 +1000:
>> Hi Mike, and sorry I missed you on IRC to discuss this there. That said, I
>> think it's great that you took this to the mailing list,
Excerpts from Jim Rollenhagen's message of 2016-03-23 14:46:16 -0700:
> On Thu, Mar 24, 2016 at 07:14:35AM +1000, Lana Brindley wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > Hi Mike, and sorry I missed you on IRC to discuss this there. That said, I
> > think it's great
Excerpts from Lana Brindley's message of 2016-03-24 07:14:35 +1000:
> Hi Mike, and sorry I missed you on IRC to discuss this there. That said, I
> think it's great that you took this to the mailing list, especially seeing
> the conversation that has ensued.
>
> More inline ...
>
> On 24/03/16
On Thu, Mar 24, 2016 at 07:14:35AM +1000, Lana Brindley wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi Mike, and sorry I missed you on IRC to discuss this there. That said, I
> think it's great that you took this to the mailing list, especially seeing
> the conversation that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Mike, and sorry I missed you on IRC to discuss this there. That said, I
think it's great that you took this to the mailing list, especially seeing the
conversation that has ensued.
More inline ...
On 24/03/16 01:06, Mike Perez wrote:
> Hey
On 23/03/16 15:00 -0400, Doug Hellmann wrote:
Excerpts from Mike Perez's message of 2016-03-23 08:06:28 -0700:
Hey all,
I've been talking to a variety of projects about lack of install guides. This
came from me not having a great experience with trying out projects in the big
tent.
Projects
On Wed, Mar 23, 2016 at 11:06 AM, Mike Perez wrote:
> Hey all,
>
> I've been talking to a variety of projects about lack of install guides.
> This
> came from me not having a great experience with trying out projects in the
> big
> tent.
>
> Projects like Manila have proposed
Excerpts from Mike Perez's message of 2016-03-23 08:06:28 -0700:
> Hey all,
>
> I've been talking to a variety of projects about lack of install guides. This
> came from me not having a great experience with trying out projects in the big
> tent.
>
> Projects like Manila have proposed install
- Original Message -
> From: "Mike Perez" <thin...@gmail.com>
> To: "OpenStack Development Mailing List (not for usage questions)"
> <openstack-dev@lists.openstack.org>
> Sent: Wednesday, March 23, 2016 12:24:55 PM
> Subject: Re: [open
On Wed, Mar 23 2016, Mike Perez wrote:
> As seen from the Manila review [1], the install docs team is suggesting these
> to be put in their developer guide.
>
> I don't think this is a great idea. Mainly because they are for developers,
> operators aren't going to be looking in there for install
On 12:05 Mar 23, Steve Gordon wrote:
> Did you look at the link I provided above?:
>
> http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-guide/source/manila.rst
>
> This content is merged.
Thanks Steve. So is this no longer a requirement that a project has to be
On 23/03/2016 16:12, Steve Gordon wrote:
> - Original Message -
>> From: "Steve Gordon"
>> To: "OpenStack Development Mailing List (not for usage questions)"
>>
>>
>> - Original Message -
>>> From: "Graham Hayes"
- Original Message -
> From: "Steve Gordon"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
>
> - Original Message -
> > From: "Steve Gordon"
> > To: "OpenStack Development
- Original Message -
> From: "Steve Gordon"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
>
> - Original Message -
> > From: "Graham Hayes" ha...@hpe.com>
> > To: "OpenStack Development Mailing List
- Original Message -
> From: "Graham Hayes"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
>
> On 23/03/2016 15:37, Steve Gordon wrote:
> > - Original Message -
> >> From: "Mike Perez"
On 23/03/2016 15:37, Steve Gordon wrote:
> - Original Message -
>> From: "Mike Perez"
>> To: "OpenStack Development Mailing List"
>>
>> Hey all,
>>
>> I've been talking to a variety of projects about lack of install guides. This
>>
On 11:34 Mar 23, Steve Gordon wrote:
> Are there examples of projects that have this user orientated install
> documentation written but are actively being rejected from including it in
> the install guide (in the Magnum case it has been pushed out to Newton as it
> was a late submission, not
- Original Message -
> From: "Mike Perez"
> To: "OpenStack Development Mailing List"
>
> Hey all,
>
> I've been talking to a variety of projects about lack of install guides. This
> came from me not having a great experience with
Hey all,
I've been talking to a variety of projects about lack of install guides. This
came from me not having a great experience with trying out projects in the big
tent.
Projects like Manila have proposed install docs [1], but they were rejected
by the install docs team because it's not in
49 matches
Mail list logo