From: Tomas Sedovic tsedovic@redhat.com
The `next` branch has the latest & greatest. However, git checks out `master` by default. This mentions the fact in getting started guide. --- getting_started.txt | 9 +++++++++ 1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/getting_started.txt b/getting_started.txt index 9cd66c7..db4041e 100644 --- a/getting_started.txt +++ b/getting_started.txt @@ -55,6 +55,15 @@ $ git clone git://git.fedorahosted.org/git/deltacloud/docs.git/ $ git clone git://git.fedorahosted.org/git/deltacloud/portal.git/ - The deltacloud aggregator code
+Switch the `docs` and `portal` repositories to the "next" branch: + +$ cd docs +$ git checkout -t origin/next +$ cd ../portal +$ git checkout -t origin/next + +This will get you to the latest and greatest stuff. + Installing packages ------------------- In order to make the deltacloud components work, you'll need to
From: Tomas Sedovic tsedovic@redhat.com
--- getting_started.txt | 12 +++++++++--- 1 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/getting_started.txt b/getting_started.txt index db4041e..4fa880d 100644 --- a/getting_started.txt +++ b/getting_started.txt @@ -64,6 +64,7 @@ $ git checkout -t origin/next
This will get you to the latest and greatest stuff.
+ Installing packages ------------------- In order to make the deltacloud components work, you'll need to @@ -73,12 +74,17 @@ packages may vary): rubygem-rails rubygem-daemons rubygem-gettext_rails -postgresql -postgresql-server -ruby-postgres +rubygem-sqlite3-ruby rubygem-compass (this is not yet in Fedora, so you'll have to gem install) rubygem-haml (this is not yet in Fedora, so you'll have to gem install)
+If you want to develop using PostgreSQL database instead of the default SQLite, install these, too: + +ruby-postgres +postgresql +postgresql-server + + Postgresql database setup ------------------------- Once you have the proper packages installed you have to setup the
From: Tomas Sedovic tsedovic@redhat.com
--- getting_started.txt | 16 ++++++++++++++-- 1 files changed, 14 insertions(+), 2 deletions(-)
diff --git a/getting_started.txt b/getting_started.txt index 4fa880d..47570a1 100644 --- a/getting_started.txt +++ b/getting_started.txt @@ -78,14 +78,26 @@ rubygem-sqlite3-ruby rubygem-compass (this is not yet in Fedora, so you'll have to gem install) rubygem-haml (this is not yet in Fedora, so you'll have to gem install)
-If you want to develop using PostgreSQL database instead of the default SQLite, install these, too: +If you want to develop using PostgreSQL database instead of the default SQLite, +install these, too:
ruby-postgres postgresql postgresql-server
-Postgresql database setup +Database +-------- +For development purposes we're using SQLite database which is much easier to +set up. + +However, we _strongly_ suggest using more suitable replacement (such as +PostgreSQL) in production. + +If you want to set up PostgreSQL, read the following section. SQLite users may +skip it and continue with "Setting up the drivers". + +PostgreSQL database setup ------------------------- Once you have the proper packages installed you have to setup the postgresql database. As root:
On Fri, Mar 12, 2010 at 1:31 PM, tsedovic@redhat.com wrote:
From: Tomas Sedovic tsedovic@redhat.com
getting_started.txt | 16 ++++++++++++++-- 1 files changed, 14 insertions(+), 2 deletions(-)
diff --git a/getting_started.txt b/getting_started.txt index 4fa880d..47570a1 100644 --- a/getting_started.txt +++ b/getting_started.txt @@ -78,14 +78,26 @@ rubygem-sqlite3-ruby rubygem-compass (this is not yet in Fedora, so you'll have to gem install) rubygem-haml (this is not yet in Fedora, so you'll have to gem install)
-If you want to develop using PostgreSQL database instead of the default SQLite, install these, too: +If you want to develop using PostgreSQL database instead of the default SQLite, +install these, too:
ruby-postgres postgresql postgresql-server
-Postgresql database setup +Database +-------- +For development purposes we're using SQLite database which is much easier to +set up.
+However, we _strongly_ suggest using more suitable replacement
Just a minor grammatical fix ^ 'using a more suitable'
(such as +PostgreSQL) in production.
+If you want to set up PostgreSQL, read the following section. SQLite users may +skip it and continue with "Setting up the drivers".
+PostgreSQL database setup
Once you have the proper packages installed you have to setup the postgresql database. As root: -- 1.6.6.1
deltacloud-devel mailing list deltacloud-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/deltacloud-devel
From: Tomas Sedovic tsedovic@redhat.com
The getting started guide contained an old version way of starting the server. This is a fix. --- getting_started.txt | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/getting_started.txt b/getting_started.txt index 47570a1..eb4cd59 100644 --- a/getting_started.txt +++ b/getting_started.txt @@ -136,7 +136,9 @@ rest of the drivers should be similar, although may require some additional gems be installed.
$ cd path/to/deltacloud/core/server/bin -$ ./deltacloudd mock +$ ./deltacloudd -i mock + +This will run the deltacloud core server on port 3001.
Setting up the aggregator -------------------------
From: Tomas Sedovic tsedovic@redhat.com
SQLite database migration steps were missing from the getting started guide. --- getting_started.txt | 25 ++++++++++++++++++++----- 1 files changed, 20 insertions(+), 5 deletions(-)
diff --git a/getting_started.txt b/getting_started.txt index eb4cd59..90969ff 100644 --- a/getting_started.txt +++ b/getting_started.txt @@ -145,10 +145,25 @@ Setting up the aggregator Now we need to setup the aggregator (which includes the UI). As your normal user:
-$ cd path/to/deltacloud/portal/src -$ rake db:create:all -$ rake db:migrate -$ rake db:test:prepare + +For SQLite: + $ cd path/to/deltacloud/portal/src/config + $ mv database.sqlite database.yml + + Prepare the database (as root): + + # rake db:migrate + # cd ../db + + You should see the development.sqlite file. Change its ownership to the user that will be run the aggregator: + + # chown someuser:somegroup development.sqlite3 + +For PostgreSQL: + $ cd path/to/deltacloud/portal/src + $ rake db:create:all + $ rake db:migrate + $ rake db:test:prepare
If all went well here, then the database should be ready for you to start up the aggregator. We also have to set it up so that @@ -159,7 +174,7 @@ $ ln -s /absolute/path/to/deltacloud/core/client \
You can now run the UI:
-$ ./script/server -p 3001 +$ ./script/server
Which will start up the UI. There is one more piece to start up before we can actually run, and that is taskomatic.
From: Tomas Sedovic tsedovic@redhat.com
We no longer use tascomatic. --- getting_started.txt | 14 ++------------ 1 files changed, 2 insertions(+), 12 deletions(-)
diff --git a/getting_started.txt b/getting_started.txt index 90969ff..5ffbef5 100644 --- a/getting_started.txt +++ b/getting_started.txt @@ -176,18 +176,8 @@ You can now run the UI:
$ ./script/server
-Which will start up the UI. There is one more piece to start -up before we can actually run, and that is taskomatic. - -Setting up taskomatic ---------------------- -Taskomatic is the component that actually runs tasks in -response to user action. It lives inside the portal -code and uses the same database schema as the portal. -To run it, you just need to: - -$ cd path/to/deltacloud/portal/src/task-omatic -$ RAILS_ENV=development ./taskomatic.rb -n +Which will start up the aggregator UI on port 3000. There is one more piece to +start up before we can actually run, and that is taskomatic.
Checking out the UI -------------------
On Fri, Mar 12, 2010 at 1:31 PM, tsedovic@redhat.com wrote:
From: Tomas Sedovic tsedovic@redhat.com
We no longer use tascomatic.
getting_started.txt | 14 ++------------ 1 files changed, 2 insertions(+), 12 deletions(-)
diff --git a/getting_started.txt b/getting_started.txt index 90969ff..5ffbef5 100644 --- a/getting_started.txt +++ b/getting_started.txt @@ -176,18 +176,8 @@ You can now run the UI:
$ ./script/server
-Which will start up the UI. There is one more piece to start -up before we can actually run, and that is taskomatic.
-Setting up taskomatic
-Taskomatic is the component that actually runs tasks in -response to user action. It lives inside the portal -code and uses the same database schema as the portal. -To run it, you just need to:
-$ cd path/to/deltacloud/portal/src/task-omatic -$ RAILS_ENV=development ./taskomatic.rb -n +Which will start up the aggregator UI on port 3000. There is one more piece to +start up before we can actually run, and that is taskomatic.
This last sentence ^ should be removed, as the separate taskomatic process is now gone.
Checking out the UI
From: Tomas Sedovic tsedovic@redhat.com
Getting started guide suggested to run the `rake db:migrate` step as root. However, it's not necessary and complicates the setup process (permissions etc. must be set afterwards). --- getting_started.txt | 11 ++--------- 1 files changed, 2 insertions(+), 9 deletions(-)
diff --git a/getting_started.txt b/getting_started.txt index 5ffbef5..1f72258 100644 --- a/getting_started.txt +++ b/getting_started.txt @@ -149,15 +149,8 @@ As your normal user: For SQLite: $ cd path/to/deltacloud/portal/src/config $ mv database.sqlite database.yml - - Prepare the database (as root): - - # rake db:migrate - # cd ../db - - You should see the development.sqlite file. Change its ownership to the user that will be run the aggregator: - - # chown someuser:somegroup development.sqlite3 + $ rake db:migrate + $ cd ../db
For PostgreSQL: $ cd path/to/deltacloud/portal/src
On Fri, Mar 12, 2010 at 1:31 PM, tsedovic@redhat.com wrote:
From: Tomas Sedovic tsedovic@redhat.com
Getting started guide suggested to run the `rake db:migrate` step as root. However, it's not necessary and complicates the setup process (permissions etc. must be set afterwards).
getting_started.txt | 11 ++--------- 1 files changed, 2 insertions(+), 9 deletions(-)
diff --git a/getting_started.txt b/getting_started.txt index 5ffbef5..1f72258 100644 --- a/getting_started.txt +++ b/getting_started.txt @@ -149,15 +149,8 @@ As your normal user: For SQLite: $ cd path/to/deltacloud/portal/src/config $ mv database.sqlite database.yml
- Prepare the database (as root):
- # rake db:migrate
- # cd ../db
- You should see the development.sqlite file. Change its ownership to
the user that will be run the aggregator:
- # chown someuser:somegroup development.sqlite3
- $ rake db:migrate
You should still run rake db:create:all before migrate, even for sqlite
+ $ cd ../db
For PostgreSQL: $ cd path/to/deltacloud/portal/src -- 1.6.6.1
deltacloud-devel mailing list deltacloud-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/deltacloud-devel
From: Tomas Sedovic tsedovic@redhat.com
In the getting started guide. --- getting_started.txt | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/getting_started.txt b/getting_started.txt index 1f72258..b40586e 100644 --- a/getting_started.txt +++ b/getting_started.txt @@ -152,6 +152,8 @@ For SQLite: $ rake db:migrate $ cd ../db
+ You should see the "development.sqlite" file there. + For PostgreSQL: $ cd path/to/deltacloud/portal/src $ rake db:create:all
On Fri, Mar 12, 2010 at 1:31 PM, tsedovic@redhat.com wrote:
From: Tomas Sedovic tsedovic@redhat.com
In the getting started guide.
getting_started.txt | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/getting_started.txt b/getting_started.txt index 1f72258..b40586e 100644 --- a/getting_started.txt +++ b/getting_started.txt @@ -152,6 +152,8 @@ For SQLite: $ rake db:migrate $ cd ../db
- You should see the "development.sqlite" file there.
For PostgreSQL: $ cd path/to/deltacloud/portal/src $ rake db:create:all -- 1.6.6.1
This wasn't in your patchset, but since it is right below the db stuff -
could you please remove this line:
$ ln -s /absolute/path/to/deltacloud/core/client \ /absolute/path/to/deltacloud/portal/src/vendor/plugins
^^ is no longer accurate, as aggregator uses the core/client _gem_. The directions should just list that gem as a dependency (gem install deltacloud-client). Note this gem can also be built locally if there is something the developer wants to get that is newer than what is on gemcutter. Build is just: gem build <core/client>/deltacloud-client.gem gem install <name>.gem
Overall, this looks like a good series of improvements. I'll have a few comments/minor corrections in individual patches, but now that I have looked at the series, I think it would be simpler and clearer if this were all squashed into one commit.
On Fri, Mar 12, 2010 at 1:30 PM, tsedovic@redhat.com wrote:
From: Tomas Sedovic tsedovic@redhat.com
The `next` branch has the latest & greatest. However, git checks out `master` by default. This mentions the fact in getting started guide.
getting_started.txt | 9 +++++++++ 1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/getting_started.txt b/getting_started.txt index 9cd66c7..db4041e 100644 --- a/getting_started.txt +++ b/getting_started.txt @@ -55,6 +55,15 @@ $ git clone git:// git.fedorahosted.org/git/deltacloud/docs.git/ $ git clone git://git.fedorahosted.org/git/deltacloud/portal.git/
- The deltacloud aggregator code
+Switch the `docs` and `portal` repositories to the "next" branch:
+$ cd docs +$ git checkout -t origin/next +$ cd ../portal +$ git checkout -t origin/next
+This will get you to the latest and greatest stuff.
Installing packages
In order to make the deltacloud components work, you'll need to
1.6.6.1
deltacloud-devel mailing list deltacloud-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/deltacloud-devel
deltacloud-devel@lists.fedorahosted.org