I tried it out. After a vagrant up I found the host directory seemed to be mounted in /home/vagrant/sync
This is slightly counter to what most vagrant boxes do though where the hosts folder is found at /vagrant
How are you building these? I've built CentOS6 and CentOS7 boxes before by hand but I'm wondering what your doing to automate them with CBS. Packer?
On 15 Apr 13:58, Ben Hosmer wrote:
I tried it out. After a vagrant up I found the host directory seemed to be mounted in /home/vagrant/sync
This is annoying but it is also the case with official centos images.
On 4/15/16 7:58 PM, Ben Hosmer wrote:
I tried it out. After a vagrant up I found the host directory seemed to be mounted in /home/vagrant/sync
This is slightly counter to what most vagrant boxes do though where the hosts folder is found at /vagrant
Sorry, I should have mentioned that (I thought that everyone is an existing user of the official centos/7 Vagrant images from Atlas, which already behaved like this). There's an older pull request in the official repo, not yet accepted. [1]
I would also like the sync folder to become the Vagrant default; it is confusing for new users, and annoying for people using the same Vagrantfile with different distros.
How are you building these? I've built CentOS6 and CentOS7 boxes before by hand but I'm wondering what your doing to automate them with CBS. Packer?
CBS already had support for building images (automated via Kickstart, see the official repo), I just added support for CentOS 6. [2]
Regards, Laurențiu
[1] https://github.com/CentOS/sig-cloud-instance-build/pull/34 [2] https://github.com/CentOS/sig-cloud-instance-build/tree/master/vagrant
On 16/04/16 09:23, Laurentiu Pancescu wrote:
I would also like the sync folder to become the Vagrant default; it is confusing for new users, and annoying for people using the same Vagrantfile with different distros.
If we can find a good way to communicate this change to existing users, lets make the change.
So, how would we communicate this ?
the underlaying concern is that anyone who has not set a custom path, would suddenly find everything broken, if they were to do a refresh on the new releases right ?
regards,
On 4/17/16 1:07 AM, Karanbir Singh wrote:
On 16/04/16 09:23, Laurentiu Pancescu wrote:
I would also like the sync folder to become the Vagrant default
If we can find a good way to communicate this change to existing users, lets make the change.
So, how would we communicate this ?
Perhaps we could announce a date for actually implementing this change, 2 to 3 months from now (not sure what a reasonable transition time would be) - this should be enough time for people impacted by this change to adjust their setups. We could communicate this via an initial announcement on the centos, centos-announce, and language-specific user mailing lists, maybe followed by monthly reminders until the change occurs. And explicitly state this change in the release notes on Atlas. Maybe also a post on the Facebook group you mentioned on your blog?
Should we first ask on the CentOS user mailing lists for significant objections from existing users?
the underlaying concern is that anyone who has not set a custom path, would suddenly find everything broken, if they were to do a refresh on the new releases right ?
Yes, unfortunately. Hopefully communicating this in advance will minimize the impact.
Regards, Laurențiu
Just release note it... - next revision note that it will be changing - revision after that do it and release note you did it.
Or you could crutch it for a release with a symlink but those crutches never seem to get removed.
-- Vince Skahan Infrastructure Engineering and Support Office of Research Information Services (ORIS)
-----Original Message----- From: centos-devel-bounces@centos.org [mailto:centos-devel-bounces@centos.org] On Behalf Of Laurentiu Pancescu Sent: Sunday, April 17, 2016 12:41 AM To: The CentOS developers mailing list. centos-devel@centos.org Subject: Re: [CentOS-devel] Vagrant CentOS 6 Boxes
On 4/17/16 1:07 AM, Karanbir Singh wrote:
On 16/04/16 09:23, Laurentiu Pancescu wrote:
I would also like the sync folder to become the Vagrant default
If we can find a good way to communicate this change to existing users, lets make the change.
So, how would we communicate this ?
Perhaps we could announce a date for actually implementing this change, 2 to 3 months from now (not sure what a reasonable transition time would be) - this should be enough time for people impacted by this change to adjust their setups. We could communicate this via an initial announcement on the centos, centos-announce, and language-specific user mailing lists, maybe followed by monthly reminders until the change occurs. And explicitly state this change in the release notes on Atlas. Maybe also a post on the Facebook group you mentioned on your blog?
Should we first ask on the CentOS user mailing lists for significant objections from existing users?
the underlaying concern is that anyone who has not set a custom path, would suddenly find everything broken, if they were to do a refresh on the new releases right ?
Yes, unfortunately. Hopefully communicating this in advance will minimize the impact.
Regards, Laurențiu _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 18/04/16 15:48, Vince Skahan wrote:
Just release note it...
- next revision note that it will be changing
- revision after that do it and release note you did it.
Or you could crutch it for a release with a symlink but those crutches never seem to get removed.
We can likely ensure it goes. otoh, it wont break for people with existing deploys - and create the option for new setups
-
Ben Hosmer -
Julien Pivotto -
Karanbir Singh -
Laurentiu Pancescu -
Vince Skahan