I'm the product lead on cloud.gov... Thanks for noticing us! There are other Cloud Foundry deployments, but what makes cloud.gov special is the focus on ensuring federal agencies are actually able to use it. Federal compliance for a cloud service provider is a tough bar to clear, and without it most agencies are simply unable to take advantage of capabilities the rest of the world now takes for granted. That in turn…
Please let the public use it
Cloud.gov
111–120 of 125 posts
Re: Cloud.gov
#112I'm the product lead on cloud.gov... Thanks for noticing us! There are other Cloud Foundry deployments, but what makes cloud.gov special is the focus on ensuring federal agencies are actually able to use it. Federal compliance for a cloud service provider is a tough bar to clear, and without it most agencies are simply unable to take advantage of capabilities the rest of the world now takes for granted. That in turn…
I could easily see how the government's business process could be at conflict with the commercial sector's business process. Colluding the two in even a single Open Source project would seem to be illogical.
Re: Cloud.gov
#113Earlier quoted context omitted.
This is totally a minor thing, but I feel like the icons halfway down the page are off-by-one: http://i.imgur.com/bXTZqOZ.png That is, the arrowbox thingie for scalability, the lock for security, etc?
Good eyes, will see if we can fix that.
Re: Cloud.gov
#114Re: Cloud.gov
#115Earlier quoted context omitted.
Good eyes, will see if we can fix that.
Another very minor thing is that when I click anywhere inside the section below the header, a light-grey border shows up. http://imgur.com/qaqvozK
Re: Cloud.gov
#116Earlier quoted context omitted.
Look at job ads. Many, many companies of all sizes ask for experience working with massively distributed architectures, "over 1,000 servers" and things like that.
FWIW I built and worked on a server farm of upwards of 2,000 physical servers with myself and one other. (with minor labour support from another team of 3 people when needed). it's possible to work in a small team and be effective even at large scale.
Re: Cloud.gov
#117Earlier quoted context omitted.
If that happens to you in the future, be honest and say that the other interviewer already asked you the same questions. Not doing so probably worked against you, as someone probably realized at some point that the same questions had been asked, and then they looked at each other in confusion wondering "Why didn't this guy say something?"
The funny thing was, in interview #2 I did mention that that they were asking me all the same questions, once it became clear that that was happening. The interviewer was like, "Oh? Really? Well this is our interview process," and then kept going. And these were 30-45 minute phone interviews, too. It was really strange.
Re: Cloud.gov
#118Earlier quoted context omitted.
I would do it, but why do they have to base you in SF? You should be able to stay local to where you are actually helping.
I think there might be state-based chapters? My friends here are actually part of "Code for Maine."
Re: Cloud.gov
#119As someone who develops for a Gov't agency, this is the wrong move. So much money has been spent on mimicking the private sector innovators. Millions and millions of tax dollars spent on these type of projects. The focus really needs to be on building a process to better integrate private cloud services and gov't applications. I mean they already are for the most part: https://aws.amazon.com/compliance/fedramp/ https…
You listed two IaaS provider and one SaaS provider. cloud.gov is a PaaS provider. There is no FedRAMP PaaS available to agencies, and PaaS is the level of abstraction needed to accelerate delivery of services the government itself provides. We also leverage the fact that AWS GovCloud already has FedRAMP status as an IaaS to accelerate our delivery of cloud.gov (which sits on top of it), so we're piggy-backing on the…
Re: Cloud.gov
#120Earlier quoted context omitted.
You listed two IaaS provider and one SaaS provider. cloud.gov is a PaaS provider. There is no FedRAMP PaaS available to agencies, and PaaS is the level of abstraction needed to accelerate delivery of services the government itself provides. We also leverage the fact that AWS GovCloud already has FedRAMP status as an IaaS to accelerate our delivery of cloud.gov (which sits on top of it), so we're piggy-backing on the…
Actually, there are several FedRAMP PaaS' available to agencies. A quick look at https://www.fedramp.gov/marketplace/compliant-systems/ lists several compliant PaaS offerings, including one (Autonomic Resources LLC – ARCWRX) based on OpenShift. It's great to see activity in this space.
http://www.fedramp.gov/marketplace/compliant-systems/blackme...
http://www.fedramp.gov/marketplace/compliant-systems/autonom...
Both built on Red Hat OpenShift