rename box prefixes to bento- instead of opscode-

[juliandunn]

• Opscode is now Chef Software
• Since these boxes are used by and for other purposes than Chef, rather than putting the company name in there, we should change the prefix to 'bento-'
• Rebuild and publish all boxes
• Coordinate with Fletcher Nichol to update test-kitchen URLs
• Stretch goal: Get Chef Ops to put Cloudfront in front of the S3 bucket, to speed up downloads

[bflad]

👍 need any help?

[juliandunn]

@bflad If you want to go ahead and do the search-and-replace and rebuild things to make sure they didn't break, I would take the PR!

[bflad]

Opened test-kitchen/kitchen-vagrant#92 to hopefully address 4th bullet point.

[sethvargo]

@juliandunn I talked with Mitchell about this and I have a WIP branch on bento. We are actually going to rename them to just OS-version (ubuntu-12.04). With Vagrant Cloud, we have namespacing. So people can use chef/ubuntu-12.04 in their Vagrantfiles.

[juliandunn]

@sethvargo What do the boxes get installed as locally when you 'vagrant box list'? And what about the users on Vagrant < 1.5.x?

[sethvargo]

@juliandunn

$ vagrant box list
boot2docker-0.5.4-1  (vmware_desktop, 0)
chef/debian-7.4      (vmware_desktop, 0)
chef/ubuntu-12.04    (vmware_desktop, 0)
opscode-centos-5.10  (virtualbox, 0)
opscode-centos-5.10  (vmware_desktop, 0)
# ...

I don't think it's unreasonable to require a minimum version of 1.5 for Vagrant.

[juliandunn]

Cool.

Yeah, and since we don't delete old boxes (by design), it's probably safe to tableflip things.

[sethvargo]

Cool. I'll work on that by the pool

[tknerr]

@sethvargo @juliandunn so are the vagrantcloud boxes always up-to-date?

If so, should we link them in the README instead?

Right now it's a bit confusing, because I don't know whether the S3 boxes and vagrantcloud boxes are actually in sync...

[juliandunn]

@tknerr The Vagrantcloud boxes are always up-to-date but it's a manual process for now (i.e. I do it). I'm doing a minimal amount of work on Bento until @sethvargo 's team has more time to devote to it.

[tknerr]

@juliandunn thanks!

[flaccid]

For me the main one outstanding that will really help now is cloudfront support for the boxes (which currently is just S3 bucket opscode-vm-bento.s3.amazonaws.com in us-west-1 afaik).
Down here in Australia some of the routes overseas plain suck even when on cable or better - box download can literally be 1 or more hours.

[cheeseplus]

Closing this issue as we're moving everything to Atlas which takes care of namespacing https://atlas.hashicorp.com/bento @8a424e2900148bb8d732604844b4e18bce064d07