Open Stack

Hi Diane,
I think there may be another way to achieve what you want without
needing as many conditions, but I'd want to make sure I understand what
you're doing. Next time we're in the same office at the same time, let's
talk about it.

Regards,
David

On 10/01/2013 09:46 AM, Diane Fleming wrote:
> Summer, 
> 
> It does seem backwards, but it's not.
> 
> Without conditions, if I include a file, it pulls everything in by
> default. 
> 
> (And this file should live in the config-reference folder.)
> 
> With conditions, it excludes anything it does not meet the conditions for.
> 
> I couldn't figure out a way to do it the way you're talking about.
> 
> Anyway, I'm going to abandon this change for now and open a bug for it for
> icehouse. 
> 
> Anne clarified that there are two different audiences, and a different
> slant on the content for each audience.
> 
> I'll open another bug for that, and I won't end up using conditions to
> make this happen.
> 
> Also, I'll post information about using conditions (profiling) on the wiki.
> 
> Diane
> ----------------------------------------------
> Diane Fleming
> Software Developer II - US
> 
> diane.fleming at rackspace.com
> Cell  512.323.6799
> Office 512.874.1260
> Skype drfleming0227
> Google-plus diane.fleming at gmail.com
> 
> 
> 
> 
> 
> 
> On 9/30/13 10:46 PM, "Summer Long" <slong at redhat.com> wrote:
> 
>> So, am sure there's a good reason, but that seems backwards. That is,
>> wouldn't the odd piece out be tagged with the condition? That is, the
>> file is slotted under the config reference so shouldn't need to have the
>> condition of belonging to the config reference. Any person updating the
>> file for another bug wouldn't automatically think to add a tag, and if
>> one is missed, the API will look mighty strange.
>>
>> Why not tag with an API condition? Or just split it out into a separate
>> section and include it that way?
>>
>> cheers, Summer
>>
>> ----- Original Message -----
>> From: "Diane Fleming" <diane.fleming at RACKSPACE.COM>
>> To: openstack-docs at lists.openstack.org
>> Sent: Tuesday, October 1, 2013 1:19:46 PM
>> Subject: [Openstack-docs] Hi all
>>
>> Tom Fifield asked me to make you aware of a change I'm making:
>>
>> There's a bug that requested that TempURL and FormPost be added to the
>> Object Storage API v2 Reference.
>> (https://bugs.launchpad.net/openstack-manuals/+bug/1224562)
>>
>> However, this information was already moved to the new Configuration
>> Reference. 
>>
>> Then, Anne Gentle asked that I include the TempURL and FormPost
>> information in both books.
>>
>> So, I submitted this change: https://review.openstack.org/#/c/49098 /
>> which conditionalizes content in the
>> doc/config-reference/object-storage/section_object-storage-features.xml
>> file in the Config Reference so that TempURL and FormPost are NOT
>> conditionalized (but everything else IS conditionalized).
>>
>> Then, I updated the Object Storage API v2 Reference to include this file
>> so that it picks up the TempURL and FormPost information. (
>> https://review.openstack.org/#/c/47917 /)
>>
>> The logic is, when I include a direct reference to this file from the
>> Object Storage API v2 Reference, it won't pick up the content that is
>> conditionalized, but it will pick up the non-conditionalized content.
>>
>> But in order for the second change (47917) to work, the first change
>> (49098) has to be pushed.
>>
>> Thoughts? Comments?
>>
>> Thanks, 
>>
>> Diane 
>> ----------------------------------------------
>> Diane Fleming 
>> Software Developer II - US
>> diane.fleming at rackspace.com
>> Cell 512.323.6799 
>> Office 512.874.1260
>> Skype drfleming0227
>> Google-plus diane.fleming at gmail.com
>>
>> _______________________________________________
>> Openstack-docs mailing list
>> Openstack-docs at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
> 
> 
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>