<html 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="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:2072187633;
mso-list-type:hybrid;
mso-list-template-ids:-878393808 67698711 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-number-format:alpha-lower;
mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Good morning / afternoon / evening,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Not sure if you have seen the agenda etherpad posted in the Slack channel -
<a href="https://etherpad.openstack.org/p/picasso-first-meeting">https://etherpad.openstack.org/p/picasso-first-meeting</a>. Might be worth putting our thoughts in there, I already had a few questions about integration with the OpenStack community and so on.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Here are a few of my biggest sticking points with the project which I feel we should really address early on:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">a)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">Currently the project does not appear to use the standard OpenStack Oslo libraries and as such the configuration and behavior of the project is inconsistent with other projects.
This could be particularly confusing for operators as even simple things like the config file (there isn’t one yet that I am aware of, stuff is passed In via args at daemon run time) is completely different to the usual section based config files we see in
most OpenStack projects.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:Calibri"><span style="mso-list:Ignore">b)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:Calibri">The project only works with IronFunctions, not saying that IronFunctions is a bad choice for sure a driver for IronFunctions should be included, but it would be good to allow
other Function as a Service platforms to make use of Picasso in a pluggable fashion, e.g. a driver for Fission, or a raw driver based on top of Nova / Heat. For me vendor neutrality is a really important aspect of OpenStack services and having the freedom
to choose the backend of these APIs is crucial.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Best Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Rob<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black">Derek Schultz <schultz.derek@gmail.com><br>
<b>Reply-To: </b>"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org><br>
<b>Date: </b>Tuesday, March 7, 2017 at 5:19 AM<br>
<b>To: </b>"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org><br>
<b>Subject: </b>Re: [openstack-dev] [picasso] First meeting on 7th of March<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Update: the patch to openstack-infra/irc-meetings was merged, so we should be good to go. The only change was moving the meeting time from 1800 UTC to 1700 UTC.
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Meeting details can be found here <a href="https://wiki.openstack.org/wiki/Meetings/Picasso">https://wiki.openstack.org/wiki/Meetings/Picasso</a><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Mon, Mar 6, 2017 at 6:45 PM Derek Schultz <<a href="mailto:schultz.derek@gmail.com">schultz.derek@gmail.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class="MsoNormal">All good points, it's important that we do not diverge from the community. Today I created an #openstack-functions channel on IRC and have submitted the necessary patches to the openstack-infra project-config and irc-meetings repositories.
Due to this, I may have to move the first meeting from this Tuesday to another day or week as we wait for approval.. I'll keep this thread posted as soon as I know more.
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Derek<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Thu, Mar 2, 2017 at 11:54 AM Paul Belanger <<a href="mailto:pabelanger@redhat.com" target="_blank">pabelanger@redhat.com</a>> wrote:<o:p></o:p></p>
</div>
<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">On Thu, Mar 02, 2017 at 05:41:24PM +0000, Derek Schultz wrote:<br>
> Hi Emilien,<br>
><br>
> Thanks for the feedback! I'm aware that IRC is the standard for OpenStack<br>
> folks, but at this current stage it's just easier to hold the discussion in<br>
> Slack as Picasso ties into the IronFunctions open source project and<br>
> important context would be lost if we were to maintain different chat<br>
> platforms. That said, I think we can move Picasso from Slack to IRC in the<br>
> future (once we prepare for the big tent).<br>
><br>
I agree with Emilien here, by using a proprietary platform you are potentially<br>
alienation existing openstack developers from contributing to your project.<br>
Yes IRC would be needed for big tent, but why start consuming IRC out of the<br>
gate?<br>
<br>
Are are already hosting code on <a href="http://git.openstack.org" target="_blank">
git.openstack.org</a>, seems like the next step<br>
would be to move to IRC.<br>
<br>
> Regards,<br>
> Derek Schultz<br>
><br>
> On Wed, Mar 1, 2017 at 7:49 AM Emilien Macchi <<a href="mailto:emilien@redhat.com" target="_blank">emilien@redhat.com</a>> wrote:<br>
><br>
> > On Tue, Feb 28, 2017 at 12:30 PM, Derek Schultz <<a href="mailto:schultz.derek@gmail.com" target="_blank">schultz.derek@gmail.com</a>><br>
> > wrote:<br>
> > > Hello all,<br>
> > ><br>
> > > The Picasso team will be running our first meeting next Tuesday. All<br>
> > those<br>
> > > interested in the project are welcome!<br>
> > ><br>
> > > For those of you not familiar with Picasso, it provides a platform for<br>
> > > Functions as a Service (FaaS) on OpenStack [1].<br>
> > ><br>
> > > Tuesday, March 7th, 2017 Meeting Agenda:<br>
> > > Starting at UTC 18:00<br>
> > ><br>
> > > 1. From Python to Go. (What Picasso needs from IronFunctions to implement<br>
> > > multi-tenancy)<br>
> > > 2. Blueprints [2]<br>
> > > 3. Figure out best time slot for future meetings.<br>
> > > 4. Roadmap discussion.<br>
> > ><br>
> > > How to join:<br>
> > > <a href="http://slack.iron.io" target="_blank">http://slack.iron.io</a> in the #openstack channel<br>
> ><br>
> > I would recommend using IRC for consistency with other projects.<br>
> > Nothing forces you to do so, unless you plan to apply to the Big Tent.<br>
> > My personal recommendation would be to use IRC so you can get more<br>
> > visibility, since most of OpenStack folks are on IRC (and not always<br>
> > on Slack).<br>
> ><br>
> > Good luck for your first meeting!<br>
> ><br>
> > > Etherpad: <a href="https://etherpad.openstack.org/p/picasso-first-meeting" target="_blank">
https://etherpad.openstack.org/p/picasso-first-meeting</a><br>
> > ><br>
> > > [1] <a href="https://wiki.openstack.org/wiki/Picasso" target="_blank">https://wiki.openstack.org/wiki/Picasso</a><br>
> > > [2] <a href="https://blueprints.launchpad.net/picasso" target="_blank">https://blueprints.launchpad.net/picasso</a><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > __________________________________________________________________________<br>
> > > OpenStack Development Mailing List (not for usage questions)<br>
> > > Unsubscribe:<br>
> > <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> > > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> > ><br>
> ><br>
> ><br>
> ><br>
> > --<br>
> > Emilien Macchi<br>
> ><br>
> > __________________________________________________________________________<br>
> > OpenStack Development Mailing List (not for usage questions)<br>
> > Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> ><br>
<br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><o:p></o:p></p>
</blockquote>
</div>
</blockquote>
</div>
</div>
<hr>
Rackspace Limited is a company registered in England & Wales (company registered number 03897010) whose registered office is at 5 Millington Road, Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy can be viewed at www.rackspace.co.uk/legal/privacy-policy
- This e-mail message may contain confidential or privileged information intended for the recipient. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately
by e-mail at abuse@rackspace.com and delete the original message. Your cooperation is appreciated.
</body>
</html>