Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Add the "testfarm" as a way to instantiante two test pods #14

Open
wants to merge 9 commits into
base: master
Choose a base branch
from

Conversation

cmrd-senya
Copy link
Contributor

This allows to intantiate two pods to test federation on.

"vagrant-group" vagrant plugin is used to group VMs.
The testfarm may be started with:
vagrant group up testfarm

Also requires "vagrant-hosts" plugin.

# boxes for the test suite. But nothing must change if you disable this and fall back to
# "puppetlabs/ubuntu-14.04-64-puppet".
dev.vm.box = "diaspora-pod"
dev.vm.box_url = "ftp://anonymous:@188.32.218.161/usb1_1/package.box"
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why you defined this box url ? Why cannot use the default box ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was very useful for my usecase to speed up the deployment, but pointing to some extra url is not a very good thing. I think I may automate the creation of the speed-up box and make it optional.

@cmrd-senya cmrd-senya force-pushed the testfarm branch 3 times, most recently from 599efca to 19d6009 Compare March 30, 2016 17:53
@cmrd-senya
Copy link
Contributor Author

So as you said in #15

The capistrano deployment process in development environment is only meant for testing purpose (I want to know if deployment works) and not for development.

Then I suppose I can use the development capistrano stage for my testing purposes here instead of creating a new "test" stage?

The deployment of the "development" stage now works only if set :bundle_without, [] is added to the stage definition, otherwise you get an error because some modules aren't required by bundler.

@joebew42
Copy link
Owner

joebew42 commented Apr 5, 2016

Then I suppose I can use the development capistrano stage for my testing purposes here instead of creating a new "test" stage?

If per "testing purposes" do you mean the deploy of branch "develop" in the development environment (development.diaspora.local), yes.

The deployment of the "development" stage now works only if set :bundle_without, [] is added to the stage definition, otherwise you get an error because some modules aren't required by bundler.

Maybe some last commit in "develop" branch of diaspora caused this regression. This can be fixed by modifying the config/deploy/development.rb. Can you apply these changes ?

@cmrd-senya
Copy link
Contributor Author

Maybe some last commit in "develop" branch of diaspora caused this regression. This can be fixed by modifying the config/deploy/development.rb. Can you apply these changes ?

Yes, I'll test it now to be sure and make a PR then.

@cmrd-senya
Copy link
Contributor Author

Ok, I'll close this, since my branch keeps on changing anyway and you don't look interested in this changes in upstream. Also #16 must be fixed first, because I want to use LXC here anyway.

@cmrd-senya cmrd-senya closed this Apr 12, 2016
@joebew42 joebew42 reopened this Apr 12, 2016
@joebew42
Copy link
Owner

Sorry but I didn't have time to check this pull request. I am interested to provide support for LXC and a test farm. Give me some time to review your work. I think that README.md must be change, also.

@cmrd-senya
Copy link
Contributor Author

Ok, thanks. The changes here aren't stabilized though, so I'll set this to [WIP] then. I'll report when it's more or less ready.

LXC must be added in less hacky way than here, but I'm not sure if Vagrant will allow it easily.

@cmrd-senya cmrd-senya changed the title Add the "testfarm" as a way to instantiante two test pods [WIP] Add the "testfarm" as a way to instantiante two test pods Apr 12, 2016
@cmrd-senya cmrd-senya force-pushed the testfarm branch 2 times, most recently from c5f7b80 to 0fabe19 Compare April 14, 2016 13:33
This allows to intantiate two pods to test federation on.

"vagrant-group" vagrant plugin is used to group VMs.
The testfarm may be started with:
vagrant group up testfarm

Also requires "vagrant-hosts" plugin.
This branch of "puppet/modules/diaspora" contains version with
proposed allow_username_change feature.
Also this commit updates API.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants