<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Nice to see a discussion around this! I can have understanding
for that Tomas, for sure, we all represent companies of different
sizes, so our opinions will differ.</p>
<p>Though, I like the idea of an infrastructure, that is how we
would like customers to build there solutions. <br>
</p>
<p>Even if we will have this on the agenda in Sydney at the Forum
session I strongly encourage you to continue the discussion here
by email, and would really like to have more opinions as from more
cloud representatives...</p>
<p>Cheers,<br>
Tobias<br>
</p>
<br>
<div class="moz-cite-prefix">On 2017-10-24 16:29, Jean-Daniel
Bonnetot wrote:<br>
</div>
<blockquote type="cite"
cite="mid:4D268742-202E-4881-AD4D-D3F1C9BF4FE4@corp.ovh.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
We (OVH) gonna manage a limited quantity, step by step, to avoid
issues (hackers/miners).
<div class=""><br class="">
<div class="">For example, we gonna start with a limit of 200
trials and see how it's used, if the customers are here to try
OpenStack or to mine something... How long does it take to
consume 200 trial...?</div>
<div class="">Then we'll add 200 more or 1000 if everything is
OK.</div>
<div class="">Of course we'll try to not have a blank period
between 2 batches.<br class="">
<div class=""><br class="webkit-block-placeholder">
</div>
<div class="">Like many public cloud providers, we used to
have a lot of users with bad intentions. We'll manage it as
usual.</div>
<div class=""><br class="">
</div>
<div class="">About the reference infrastructure, I suggest to
keep the idea of an infrastructure, not a stand alone
instance.</div>
<div class="">
<div style="color: rgb(0, 0, 0); font-variant-caps: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
word-wrap: break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space;" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode:
space; -webkit-line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); font-variant-caps:
normal; letter-spacing: normal; text-align: start;
text-indent: 0px; text-transform: none; white-space:
normal; word-spacing: 0px; -webkit-text-stroke-width:
0px;">
<br class="Apple-interchange-newline">
Jean-Daniel Bonnetot</div>
<div style="color: rgb(0, 0, 0); font-variant-caps:
normal; letter-spacing: normal; text-align: start;
text-indent: 0px; text-transform: none; white-space:
normal; word-spacing: 0px; -webkit-text-stroke-width:
0px;">
<a href="http://ovh.com" class=""
moz-do-not-send="true">ovh.com</a> | @pilgrimstack</div>
<div style="font-family: 'Lucida Sans'; font-size: 14px;
font-weight: normal; font-style: normal; color: rgb(0,
0, 0); font-variant-caps: normal; letter-spacing:
normal; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;"
class="">
<br class="">
</div>
<br class="Apple-interchange-newline">
</div>
</div>
<br class="Apple-interchange-newline" style="color: rgb(0,
0, 0); font-family: 'Lucida Sans'; font-size: 14px;
font-style: normal; font-variant-caps: normal;
font-weight: normal; letter-spacing: normal; text-align:
start; text-indent: 0px; text-transform: none;
white-space: normal; word-spacing: 0px;
-webkit-text-stroke-width: 0px;">
<br class="Apple-interchange-newline">
</div>
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 24 Oct 2017, at 15:27, Tomáš Vondra <<a
href="mailto:vondra@homeatcloud.cz" class=""
moz-do-not-send="true">vondra@homeatcloud.cz</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">Hi!<br class="">
We would prefer a lower quota and/or duration of the
trial.<br class="">
<br class="">
For one, if someone finds a reference architecture for
Bitcoin mining, he could do quite a lot of damage on 8
CPUs.<br class="">
<br class="">
For two, I think the reference architecture is too
complex. It is not something one would actually build
to test a cloud. As for me, I would run one VM and do
some low-level benchmarks.<br class="">
On a conference workshop, I gave away accounts with a
quota of 2/2/20, and we have fit in 2 instances of
Wordpress, one of HAProxy and one of MySQL because we
also offer a 0,5 CPU 0,5 RAM and 5 disk flavor. The
user could also launch one instance of 2/2/20 and do
some benchmarking if they wanted.<br class="">
<br class="">
The other possibility is to limit the number of
concurrent trial accounts, which is I think also
something that was said in these discussion circles.
Etherpad, maybe?<br class="">
Tomas from Homeatcloud<br class="">
<br class="">
-----Original Message-----<br class="">
From: Tobias Rydberg [<a
href="mailto:tobias@citynetwork.se" class=""
moz-do-not-send="true">mailto:tobias@citynetwork.se</a>]
<br class="">
Sent: Monday, October 23, 2017 4:45 PM<br class="">
To: Jean-Daniel Bonnetot<br class="">
Cc: <a href="mailto:passport@openstack.org" class=""
moz-do-not-send="true">passport@openstack.org</a>; <a
href="mailto:user-committee@lists.openstack.org"
class="" moz-do-not-send="true">
user-committee@lists.openstack.org</a><br class="">
Subject: Re: [User-committee]
[publiccloud-wg][passport] Minimal offer<br class="">
<br class="">
On 2017-10-23 16:30, Jean-Daniel Bonnetot wrote:<br
class="">
<blockquote type="cite" class=""><br class="">
<blockquote type="cite" class="">On 22 Oct 2017, at
11:47, Tobias Rydberg <<a
href="mailto:tobias@citynetwork.se" class=""
moz-do-not-send="true">tobias@citynetwork.se</a>>
wrote:<br class="">
<br class="">
Hi,<br class="">
<br class="">
Thanks Jean-Daniel for a good initiative and a
good email!<br class="">
<br class="">
I totally agree that we need this clear reference
point for this, even though I guess it won't be a
"requirement" for the first release in Sydney,
just since it's not enough time to get consensus
in the matter.<br class="">
</blockquote>
So what is your suggestion for Sydney? Every public
cloud provider do his best without a common base?<br
class="">
</blockquote>
I would really like to have a common base for everyone
for Sydney, though I believe we will have a hard time
pull that through, hard enough to get all in with the
information needed. From my POV I will make sure that
we honor that reference specification, just to have
that said.<br class="">
<br class="">
With that said, I guess that will be the case, but we
can for sure try to push for the common spec.
Wednesday is a good opportunity for that!<br class="">
<blockquote type="cite" class="">
<blockquote type="cite" class="">Regarding the
reference infrastructure I think it's good to use
something that is already defined. I can probably
be fine with that amount of resources, even though
I generally think that half of it would be enough
as well to evaluate a cloud in a trial. But as I
said, like the reference to a reference
infrastructure...<br class="">
<br class="">
Earlier we haven't talked about Object Storage,
not all participants offer that. Could be a part
of the total storage amount any way. Also agree
that we should remove all things like traffic and
bandwidth from the equation.<br class="">
<br class="">
@Jean-Daniel - are you coming to Sydney? This is a
great topic for the "Passport Forum Session".<br
class="">
</blockquote>
Yep, I'll be there. Let's discuss it in Sydney with
pleasure.<br class="">
</blockquote>
Sounds good!<br class="">
<blockquote type="cite" class="">
<blockquote type="cite" class="">Thanks,<br class="">
Tobias Rydberg<br class="">
@tobberydberg<br class="">
<br class="">
<br class="">
On 2017-10-19 17:57, Jean-Daniel Bonnetot wrote:<br
class="">
<blockquote type="cite" class="">Hi PCWG<br
class="">
<br class="">
About the passport offering, we agreed on:<br
class="">
* The message: "valid for at least XX resources
on any participating public cloud for 1 month"<br
class="">
* To avoid value comparison, agree on a minimal
amount of resources <br class="">
a token would be valid (it's ok to offer more)<br
class="">
(<a
href="https://review.openstack.org/#/c/511252/1/doc/source/passport_progr"
class="" moz-do-not-send="true">https://review.openstack.org/#/c/511252/1/doc/source/passport_progr</a><br
class="">
am.rst)<br class="">
<br class="">
So here we have the message (XX ressources for a
period of time) and the period (1 month).<br
class="">
We need to define the minimal XX. Everybody can
offer more of course.<br class="">
<br class="">
Let's try something like that:<br class="">
- As reference infrastructure, I propose this
web app: <br class="">
<a
href="https://www.openstack.org/software/sample-configs/#web-applications"
class="" moz-do-not-send="true">https://www.openstack.org/software/sample-configs/#web-applications</a><br
class="">
- As the first goal is to try OpenStack (APIs,
fast delivery, features...) and not
performances, let keep the smallest
configuration<br class="">
<span class="Apple-tab-span" style="white-space:pre"></span>-
consider only the existing instances, not the
auto-scaling ones<br class="">
<span class="Apple-tab-span" style="white-space:pre"></span>-
each nova instance is 1vCPU, 1GB RAM, 5GB disk<br
class="">
<span class="Apple-tab-span" style="white-space:pre"></span>-
each cinder volume is 10GB<br class="">
<span class="Apple-tab-span" style="white-space:pre"></span>-
each swift repository is 10GB<br class="">
<span class="Apple-tab-span" style="white-space:pre"></span>-
consider special features as +1 instance, for
example some of us don't have the LB feature<br
class="">
<span class="Apple-tab-span" style="white-space:pre"></span>-
remove the bandwidth and traffic question from
the minimal offer<br class="">
<span class="Apple-tab-span" style="white-space:pre"></span>-
remove the heat question too (that means
metrics, triggers....)<br class="">
<br class="">
Some calculation latter, the minimal offer could
be announced like that:<br class="">
- 8 vCPUs<br class="">
- 8GB RAM<br class="">
- 40GB for local storage<br class="">
- 20GB for remote block storage<br class="">
- 10GB for object storage<br class="">
=> up and running for one month<br class="">
<br class="">
Is that ok for you?<br class="">
We can round up some values if you think it's
better, and/or group <br class="">
some parts (like storage to simplify to 100GB of
storage)<br class="">
<br class="">
So the final message from the foundation could
be:<br class="">
1. Valid for at least 8vCPUs, 8GB of RAM, 40GB
of local storage, <br class="">
20GB of remote block storage and 10GB of object
storage on any <br class="">
participating public cloud for 1 month or 2.
Valid for at least <br class="">
8vCPUs, 8GB of RAM, 100GB of storage on any
participating public <br class="">
cloud for 1 month<br class="">
<br class="">
Then to estimate your offer, you can just take
reference infrastructure as describe previously
and calculate the price for one month, or if
your billing model match with 8vCPUs, 8GB or
RAM... it's even more simple. Over that, offer
what you want depending on your marketing
strategy.<br class="">
<br class="">
How does it sound to you? Is it reasonable for
your?<br class="">
<br class="">
<br class="">
Jean-Daniel Bonnetot<br class="">
ovh.com | @pilgrimstack<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
_______________________________________________<br
class="">
User-committee mailing list<br class="">
<a class="moz-txt-link-abbreviated" href="mailto:User-committee@lists.openstack.org">User-committee@lists.openstack.org</a><br class="">
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee">http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee</a><br
class="">
</blockquote>
<br class="">
</blockquote>
</blockquote>
<br class="">
<br class="">
<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
User-committee mailing list
<a class="moz-txt-link-abbreviated" href="mailto:User-committee@lists.openstack.org">User-committee@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee">http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee</a>
</pre>
</blockquote>
<br>
</body>
</html>