Open Stack

Hi,

Thanks for bringing this topic to discussion! Sounds good that you meet 
the requirements and everything, and I like the idea to have more 
organizations like yours to join the program and offer free OpenStack to 
university and such. So, absolutely make sense to me.

Though, not sure if we will fit this in to the first release in Sydney, 
just because there isn't enough time.

@Saverio - are you or anyone from your organization coming to the Summit 
in Sydney? Would be a great opportunity to bring this to discussion at 
the "Passport Forum discussion".

Regards,
Tobias
@tobberydberg


On 2017-10-20 09:57, Saverio Proto wrote:
> Hello,
>
> I am trying to figure out if entities like SWITCH and other NRENs /
> Research institutions could participate to the passport program.
>
> The initial feedback I had is positive, and we meet the requirements
> for the minimum quota without problems.
>
> But we cant open the free trial to the general public. The best we can
> do is a free trial to the to the higher education sector globally. And
> when I say "we" is not just SWITCH but the larger scientific
> community.
> At this point I have to ask if this makes sense. Is it a reasonable thing ?
>
> thank you for your feedback.
>
> Saverio
>
>
> 2017-10-19 17:57 GMT+02:00 Jean-Daniel Bonnetot
> <jean-daniel.bonnetot at corp.ovh.com>:
>> Hi PCWG
>>
>> About the passport offering, we agreed on:
>> * The message: "valid for at least XX resources on any participating public cloud for 1 month"
>> * To avoid value comparison, agree on a minimal amount of resources a token would be valid (it's ok to offer more)
>> (https://review.openstack.org/#/c/511252/1/doc/source/passport_program.rst)
>>
>> So here we have the message (XX ressources for a period of time) and the period (1 month).
>> We need to define the minimal XX. Everybody can offer more of course.
>>
>> Let's try something like that:
>> - As reference infrastructure, I propose this web app: https://www.openstack.org/software/sample-configs/#web-applications
>> - As the first goal is to try OpenStack (APIs, fast delivery, features...) and not performances, let keep the smallest configuration
>>          - consider only the existing instances, not the auto-scaling ones
>>          - each nova instance is 1vCPU, 1GB RAM, 5GB disk
>>          - each cinder volume is 10GB
>>          - each swift repository is 10GB
>>          - consider special features as +1 instance, for example some of us don't have the LB feature
>>          - remove the bandwidth and traffic question from the minimal offer
>>          - remove the heat question too (that means metrics, triggers....)
>>
>> Some calculation latter, the minimal offer could be announced like that:
>> - 8 vCPUs
>> - 8GB RAM
>> - 40GB for local storage
>> - 20GB for remote block storage
>> - 10GB for object storage
>> => up and running for one month
>>
>> Is that ok for you?
>> We can round up some values if you think it's better, and/or group some parts (like storage to simplify to 100GB of storage)
>>
>> So the final message from the foundation could be:
>> 1. Valid for at least 8vCPUs, 8GB of RAM, 40GB of local storage, 20GB of remote block storage and 10GB of object storage on any participating public cloud for 1 month
>> or
>> 2. Valid for at least 8vCPUs, 8GB of RAM, 100GB of storage on any participating public cloud for 1 month
>>
>> 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.
>>
>> How does it sound to you? Is it reasonable for your?
>>
>>
>> Jean-Daniel Bonnetot
>> ovh.com | @pilgrimstack
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> User-committee mailing list
>> User-committee at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
> _______________________________________________
> User-committee mailing list
> User-committee at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3945 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20171022/388598f6/attachment.bin>