<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.im
{mso-style-name:im;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>This is what I get when running glance image-create:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> usage: glance image-create [--property <key=value>] [--file <FILE>]<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> [--progress]<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> <unavailable><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> Create a new image.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> Positional arguments:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> <unavailable> Please run with connection parameters set to retrieve<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> the schema for generating help for this command<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>So I wonder how I can get to the bottom of this.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Matt Kassawara [mailto:mkassawara@gmail.com] <br><b>Sent:</b> Saturday, April 11, 2015 1:39 PM<br><b>To:</b> Bernd Bausch; openstack-docs@lists.openstack.org<br><b>Subject:</b> Re: [OpenStack-docs] [install-guide] RE: What's Up Doc? Apr 10 2015<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>I'd use the conventional python-*client for all services except keystone because the Openstack client doesn't seem very complete for them. If you're using the glance client, it defaults to the v1 API and the commands from the Juno installation guide should work. If you use the v2 API, one thing changes with how to set public/private visibility.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Fri, Apr 10, 2015 at 8:11 PM, Bernd Bausch <<a href="mailto:berndbausch@gmail.com" target="_blank">berndbausch@gmail.com</a>> wrote:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><p class=MsoNormal style='margin-bottom:12.0pt'>Regarding the installation guide, I need some advice. Perhaps the docs community can help?<br><br>I am trying to install Kilo on yum-based systems using a repo from the RDO project. I have hit a few roadblocks that I have been able to deal with, but I am unsure what to do with the current one.<br><br>My questions are: Is it appropriate to ask developers about the intended way of doing things, if the old ways don’t work anymore? If yes, what are the best channels – chat, dev mailing list, personal email, …? If no, what else can I do? Do developers make such changes public somewhere?<br><br>Below is the problem I am currently trying to solve. **Note** that I am including it as an illustration what I am struggling with (more problems will show up as I continue working on this); I am not asking you to solve this particular problem for me.<br><br>So far, to upload an image to Glance, the “glance image-create” command is used. This command doesn’t work anymore as in the past, and I don't understand what the “glance help image-create” is trying to say. On the other hand, I haven’t found an equivalent command in the new “openstack” CLI client. So my question is – what is the correct way to upload an image these days.<br><br>Have a great weekend,<br><br>Bernd<br><br>From: Anne Gentle [mailto:<a href="mailto:annegentle@justwriteclick.com">annegentle@justwriteclick.com</a>]<br>Sent: Saturday, April 11, 2015 12:24 AM<br>To: <a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.openstack.org</a>; OpenStack Development Mailing List; <a href="mailto:openstack-i18n@lists.openstack.org">openstack-i18n@lists.openstack.org</a><br>Cc: Jesse Noller<br>Subject: [OpenStack-docs] What's Up Doc? Apr 10 2015<br><br><span class=im>Hi all,</span><br><br><span class=im>As you probably saw from PTL nominations last week, I'm happy to hand the docs PTL baton to Lana Brindley! I loved leading this group and thank you all for supporting me. Thank you Lana for your willingness to lead. I'm still here to bring us to the Kilo release, so this week's What's Up Doc brings sharp focus requests to everyone to work on docs. These are the top priorities that we all need to work on - devs, writers, testers, gaters, everyone.</span><br><br><span class=im>1. Bug triaging and fixing, especially for openstack-manuals. There are nearly 300 DocImpact bugs logged that we need developers to circle back to. With nearly 600 bugs overall, we need lots of focus here. To that end, I propose we hold a bug triage day. I'll send details in a separate email.</span><br><br><span class=im>2. Install Guide testing and reviewing. The Install Guide team has a published spec that will help reviewers see what's changing with the Kilo Install guide: <a href="http://specs.openstack.org/openstack/docs-specs/specs/kilo/installguide-kilo.html" target="_blank">http://specs.openstack.org/openstack/docs-specs/specs/kilo/installguide-kilo.html</a> Join them for weekly meetings Tuesdays at at 13:00 UTC (8:00 AM US CDT) in Google Hangout: <a href="https://plus.google.com/hangouts/_/calendar/a2FyaW4ua2F0aG9kZUBnbWFpbC5jb20.jj2lu2nbj71a0dan11vatdav3k" target="_blank">https://plus.google.com/hangouts/_/calendar/a2FyaW4ua2F0aG9kZUBnbWFpbC5jb20.jj2lu2nbj71a0dan11vatdav3k</a></span><br><br><span class=im>If you do nothing else but these two focus areas we'll be in good shape. There are other activities going on leading up to Vancouver but those two are top priorities.</span><br><br><span class=im>_RST Migration_</span><br><br><span class=im>We are working to resolve translation tool expectations with the i18N team. I want to publish the RST-based English End User Guide and Admin User Guide once we're all comfortable with the way forward. Daisy will discuss the implications at the next i18N team meeting Thursday at 0800 UTC, and we'll implement and communicate the plan.</span><br><br><span class=im>_Networking Guide_</span><br><br><span class=im>Next on the list is Networking Guide testing and reviewing. The Networking Guide team has a talk in Vancouver and needs to get their guide in shape for publishing. The neutron team is holding a doc day April 23. Please join in -- they'll post details in their notes.</span><br><br><span class=im>_First App Tutorial_</span><br><br><span class=im>There's also the First Application Tutorial that needs to finish the spec and needs an editing cleanup prior to publishing. Ideally that will happen before Vancouver, we need to get it to the finish line.</span><br><br><span class=im>_HA Guide_</span><br><br><span class=im>With everything else going on we need an updated spec for the HA Guide - the wiki page isn't enough. Based on this week's doc team meeting it sounds like that can go to RST as well but we need it in the spec so we can plan and cross-coordinate with the other priorities leading up to Vancouver.</span><br><br><span class=im>_Vancouver Summit _</span><br><span class=im>The docs team has four Fishbowl time slots, 2 Workroom slots, and 1 Meetup allocated now. If you'd like to discuss a cross-project idea, please use the form to suggest new ideas:</span><br><span class=im><a href="http://goo.gl/forms/S69HM6XEeb" target="_blank">http://goo.gl/forms/S69HM6XEeb</a>. You can see the current suggestions already posted here:</span><br><span class=im><a href="https://docs.google.com/spreadsheets/d/1vCTZBJKCMZ2xBhglnuK3ciKo3E8UMFo5S5lmIAYMCSE/edit?usp=sharing" target="_blank">https://docs.google.com/spreadsheets/d/1vCTZBJKCMZ2xBhglnuK3ciKo3E8UMFo5S5lmIAYMCSE/edit?usp=sharing</a></span><br><br><span class=im>Lana or I will send out an etherpad in the next week or so with topic suggestions for our allocation.</span><br><br><span class=im>Thanks,</span><br><span class=im>Anne</span><br><br><span class=im>--</span><br><span class=im>Anne Gentle</span><br><span class=im><a href="mailto:annegentle@justwriteclick.com">annegentle@justwriteclick.com</a></span><br><br><o:p></o:p></p><div><div><p class=MsoNormal>_______________________________________________<br>OpenStack-docs mailing list<br><a href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><o:p></o:p></p></div></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>