Hi Blair
Agree with you on a lot of that stuff, although on lifecycle management we
certainly have a bunch of tooling in place to handle scenarios like initial
creation of user environments ( basic network and router setup ), freezing
resources for non-payment, offboarding of customers after accou
Hi Matt,
I think your dot points make sense. And yes, I was thinking about Science
Cloud overlap. I see Science Clouds as potentially sharing most or all of
these attributes (with the notable exception being charging in terms of end
users seeing a $ figure, showback and/or instance/cpu hour quotas
Hey Blair
Now you've done it ! OK, I'll bite and have a go at categorising that a bit
:
1. Multi-tenant - tenants need clear separation
2. Self service sign up - customers on board themselves
3. Some kind of charging model in place which requires resource accounting
4. API endpoints and possibly
Hi Matt,
At considerable risk of heading down a rabbit hole... how are you defining
"public" cloud for these purposes?
Cheers,
Blair
On 21 September 2016 at 18:14, Matt Jarvis
wrote:
> Given there are quite a few public cloud operators in Europe now, is there
> any interest in a public cloud g
Hey Matt,
I think the conversation would be valuable. Historically, we have let the
Large Deployment Team incubate Public Cloud topics because of the active
members in that group. That doesn’t prevent us from organizing a session
and/or some conversation around it, though. Put it as a suggest
