As what jay said, but a nice thing about vagrant is that there're many many boxes stored on vagrantcloud(atlas) which you can download directly. Those boxes already have ssh key built-in so you can simply do vagrant up without a problem. So, to answer your question, if you set box to ubuntu/trusty64, then you don't have to worry about the ssh key issue.
2015-08-28 23:43 GMT+08:00 jay vyas <[email protected]>: > A non-broken Vagrant box should always have ssh keys or at least an ssh > user in it. > > From vagrant box docs: http://docs.vagrantup.com/v2/boxes/base.html: > > By default, Vagrant expects a "vagrant" user to SSH into the machine as. > This user should be setup with the insecure keypair > <https://github.com/mitchellh/vagrant/tree/master/keys> that Vagrant uses > as a default to attempt to SSH. Also, even though Vagrant uses key-based > authentication by default, it is a general convention to set the password > for the "vagrant" user to "vagrant". This lets people login as that user > manually if they need to. > > On Fri, Aug 28, 2015 at 11:40 AM, Zeng, Tom <[email protected]> wrote: > >> Thanks Evans and Jay for the answers. Will try debian, instead, is it >> still the case that ubuntu base images does not have vagrant ssh key, is >> this also any issue for ubuntu vm support? >> >> Thanks, >> Tom >> >> From: Evans Ye <[email protected]> >> Date: Friday, August 28, 2015 at 2:30 AM >> To: "Zeng, Tom" <[email protected]>, "[email protected]" < >> [email protected]> >> Cc: jay vyas <[email protected]> >> Subject: Re: vagrant output_ dir >> >> Allow me to reply this in bigtop user list as well. >> >> The question is: >> >> Do you have an example conf for the following to point to Ubuntu with >> local apt repo? >> >> docker-provisioner - Provision a Bigtop cluster on Docker container(s). >> Default to CentOS and 1 node. >> >> To answer this question precisely, Bigtop does not support ubuntu docker >> container deployment out of the box. If you only need to try out apt >> packages deployment on docker. We've debian instead. Just as what jay said, >> there're just two steps to do so: >> >> 1). >> $ vim ./bigtop-deploy/vm/vagrant-puppet-docker/vagrantconfig_debian.yaml >> set enable_local_repo to true >> 2). >> $ ./gradlew -Pconfig=vagrantconfig_debian.yaml docker-provisioner >> >> To give a slightly deeper view into this, the reason why bigtop don't >> support ubuntu container is just because there's no ubuntu base image that >> have vagrant ssh key inserted for vagrant to control container status. What >> we've now are centos-6 and debian-8: >> https://hub.docker.com/r/bigtop/deploy/tags/ >> I plan to provide full OS support for bigtop/deploy images so that users >> can build and test in container with the above one-liner. >> >> Now, if you'd like to test your ubuntu packages, you can use the bigtop >> VM provisioner. The downside of this is that you can't do provisioning on >> cloud environment such as EC2 since its already a VM. This way also have >> just 2 steps: >> >> 1). >> $ cd bigtop-deploy/vm/vagrant-puppet-vm >> $ vim vagrantconfig.yaml >> set box to ubuntu/trusty64 >> set enable_local_repo to true >> >> 2). >> $ vagrant up >> >> >> Hope this help. >> >> Evans >> >> >> 2015-08-28 11:27 GMT+08:00 Evans Ye <[email protected]>: >> >>> Allow me to reply this in bigtop user list as well. >>> >>> To answer the question >>> >>> >>> 2015-08-28 3:09 GMT+08:00 Zeng, Tom <[email protected]>: >>> >>>> Hey Jay and Evans, >>>> >>>> Do you have an example conf for the following to point to Ubuntu with >>>> local apt repo? >>>> >>>> docker-provisioner - Provision a Bigtop cluster on Docker >>>> container(s). Default to CentOS and 1 node. >>>> >>>> Thanks, >>>> Tom >>>> >>>> From: jay vyas <[email protected]> >>>> Date: Tuesday, May 26, 2015 at 8:31 PM >>>> To: "Zeng, Tom" <[email protected]> >>>> Subject: vagrant output_ dir >>>> >>>> Hiya tom >>>> >>>> I saw your question on IRC last night about local yum repos for vagrant >>>> >>>> Definetly the answer is yes ! Thats one of the really cool/easy things >>>> about testing bigtop w/ vagrant. >>>> >>>> Vagrant recipes definetly are designed to be able to load directly from >>>> build output directory. >>>> >>>> You can see the enable_local_yum parameter here : >>>> https://github.com/apache/bigtop/blob/master/bigtop-deploy/vm/vagrant-puppet-vm/vagrantconfig.yaml >>>> >>>> Setting this to true will add the rpms in output/ to the VM you spin up >>>> >>>> -- >>>> jay vyas >>>> >>> >>> >> > > > -- > jay vyas > >
