fathomdb / cloud Goto Github PK

Probably a cmdlet. Maybe using AWS auto-scaling?

When there's no Accept header, we seem to default to XML right now

We want it to auto-configure as part of installation

Backed by EBS.

Will be tricky to figure out how to place instances if we share a volume across instances. Probably we'll have to declare attachments at launch time, and launch the instance on the host with that volume attached. But then that host might be full...

We could also use snapshots to clone a shared disk.

Do something not-very-good initially (e.g. just fail if the host is full), and then get better in later versions.

Through horizon, which uses a fake hostname in /etc/hosts, we're getting back a fake hostname (openstack). Would be nice to fix it.

It should find lots of bugs!

Should it be moved into an ItemState? Is it the same thing?

There are some linuxisms in there

Verify that firewall rules are working correctly and configured correctly by the installation instructions

When running on EC2, we probably want to block metadata (169) access from the instances. Possible security issue if people put secrets in there, but more likely just confusing.

And it should then have firewall rules applied to it

Currently the bootstrap command will import an image, even if it already exists.

How do we upgrade instances when a new image version comes along?

Ideally through an init script

Right now it's infinite retries, tasks don't persist after restart, single machine only etc.

i.e. volumes.

This is essential for Zookeeper data.

Maybe our blob stores should also be compartmentalized?

We don't really want them to start taking traffic until they're ready.

See discussion in ComputeDerivedMetadataImpl

Copy the keys out of authorized_fathomcloud, and move them into Zookeeper.

We still need a technique for bootstrapping though.

Would be nice to have a stable id.

Metadata can differ though, so we might have to hash the metadata as well.

Probably differentiate between ephemeral, persistent & semi-persistent volumes

Missing from instance details I'd guess :-)

(This affects security group based rules)

Need to mark it for Jackson, or figure out how to force Gson.

Make sure it's safe, and then support CORS.

We can still have it be user-configurable, but I don't see why we wouldn't default on.

This came out of a discussion here:
https://news.ycombinator.com/item?id=6575584

Right now it's a little convoluted and a little fragile.

Maybe we should just move it to Python - the AWS CLI tools need Python anyway

I think I like service-noun-verb

Coordinated time is just good practice. Don't think we actually require it though.

I think it is replacing everything every time, because the id does not match.

Verify and fix!

Ideally through an init script

Either work around or hide these warnings. They're not important to the end user.

Like in PlatformLayer

Using ANSI colors in CLI output would be nice!

I think we may have to add copyright headers to all files.

Otherwise we run out of disk space fast

It would be nice to be able to generate the password recovery key offline (or even in an HSM), and just upload the public key. Then you'd need access to the private key to do password recovery.

Not terribly hard, either, I don't think :-)

In particular, for the creation timestamps

It's confusing!

Currently these are not enforced, but we should!

Tunnels are lost, but down probably fails

It would be great to just use Gson everywhere.

I think the main blocker is this issue:
https://code.google.com/p/google-gson/issues/detail?id=532

Does it make sense to enable swap?

Right now we copy the image back and forth repeatedly. Optimize this path!