Re: Toaster documentation, 1.6 release

Re: Toaster documentation, 1.6 release

[Barros Pena, Belen]

Hi Scott,

There is one more thing that needs to be documented: how to delete builds
from the Toaster database.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=4625

There is a file in the /poky/bitbake/lib/toaster directory called
manage.py. You can run that file with additional commands. There are 2
commands relevant to delete builds:

1. buildslist
This command is run ./manage.py buildslist and it will show you a
user-readable tabbed list of build ids and identification information

2. builddelete
This command is run ./manage.py <build_id> and will delete the build with
the specified id AND ALL related information (traversing the ForeignKey
relationships recursively) from the database.

Alex, feel free to add anything that might be missing above.

Since it looks like pretty much everything related to Toaster will be
documented in the wiki for 1.6, we should probably do the same with this
one too, but I might add the information to the Toaster manual in the YP
website as well.

If you have any questions, let us know.

Thanks!

Belén



On 18/03/2014 16:47, "Barros Pena, Belen" <belen.barros.pena@intel.com>
wrote:

>Hi Scott,
>
>As I mentioned, we would like to document how to set up a Toaster instance
>in a remote host. Alex Damian sent an email to the mailing list explaining
>the process back in February. This is it:
>
>https://lists.yoctoproject.org/pipermail/toaster/2014-February/000464.html
>
>We are thinking of documenting this in the wiki for the moment, with maybe
>a link to it from the existing Toaster section in the Development Manual.
>
>Just contact any of us, or the Toaster mailing list, if you have any
>questions.
>
>Thanks for your help with this!
>
>Belén
>
>-- 
>_______________________________________________
>toaster mailing list
>toaster@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/toaster

Re: Toaster documentation, 1.6 release

[Scott Rifenbark]

[-- Attachment #1: Type: text/plain, Size: 3014 bytes --]

Here is a quick section on deleting a build from the toaster database.

-----------------------------------

Deleting a Build from the Toaster Database

You can use the manage.py command, which is located in the
/poky/bitbake/lib/toaster directory to identify and delete builds from the
Toaster database.  Follow these steps to delete a build:

1. Identify the build:  Run the following command from the toaster
directory to display a user-readable, tabbed list of build IDs and
identification information:

     ./manage.py buildslist

2. Delete a specific build: Using the build ID displayed in the previous
step, run the following command to delete a specific build:

     ./manage.py <build_id>

The build and all related information is deleted from the Toaster
database.  The deletion operation traverses the ForeignKey relationships
recursively.




On Wed, Mar 19, 2014 at 10:52 AM, Barros Pena, Belen <
belen.barros.pena@intel.com> wrote:

> Hi Scott,
>
> There is one more thing that needs to be documented: how to delete builds
> from the Toaster database.
>
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=4625
>
> There is a file in the /poky/bitbake/lib/toaster directory called
> manage.py. You can run that file with additional commands. There are 2
> commands relevant to delete builds:
>
> 1. buildslist
> This command is run ./manage.py buildslist and it will show you a
> user-readable tabbed list of build ids and identification information
>
> 2. builddelete
> This command is run ./manage.py <build_id> and will delete the build with
> the specified id AND ALL related information (traversing the ForeignKey
> relationships recursively) from the database.
>
> Alex, feel free to add anything that might be missing above.
>
> Since it looks like pretty much everything related to Toaster will be
> documented in the wiki for 1.6, we should probably do the same with this
> one too, but I might add the information to the Toaster manual in the YP
> website as well.
>
> If you have any questions, let us know.
>
> Thanks!
>
> Belén
>
>
>
> On 18/03/2014 16:47, "Barros Pena, Belen" <belen.barros.pena@intel.com>
> wrote:
>
> >Hi Scott,
> >
> >As I mentioned, we would like to document how to set up a Toaster instance
> >in a remote host. Alex Damian sent an email to the mailing list explaining
> >the process back in February. This is it:
> >
> >
> https://lists.yoctoproject.org/pipermail/toaster/2014-February/000464.html
> >
> >We are thinking of documenting this in the wiki for the moment, with maybe
> >a link to it from the existing Toaster section in the Development Manual.
> >
> >Just contact any of us, or the Toaster mailing list, if you have any
> >questions.
> >
> >Thanks for your help with this!
> >
> >Belén
> >
> >--
> >_______________________________________________
> >toaster mailing list
> >toaster@yoctoproject.org
> >https://lists.yoctoproject.org/listinfo/toaster
>
>

[-- Attachment #2: Type: text/html, Size: 4110 bytes --]

Re: Toaster documentation, 1.6 release

[Barros Pena, Belen]

Thanks, Scott. Looks great to me, but folks on this list might have some
feedback.

Cheers

Belén

On 19/03/2014 21:55, "Scott Rifenbark" <srifenbark@gmail.com> wrote:

>Here is a quick section on deleting a build from the toaster database.
>
>-----------------------------------
>
>Deleting a Build from the Toaster Database
>
>
>You can use the manage.py command, which is located in the
>/poky/bitbake/lib/toaster directory to identify and delete builds from
>the Toaster database.  Follow these steps to delete a build:
>
>
>1. Identify the build:  Run the following command from the toaster
>directory to display a user-readable, tabbed list of build IDs and
>identification information:
>
>
>     ./manage.py buildslist
>
>
>2. Delete a specific build: Using the build ID displayed in the previous
>step, run the following command to delete a specific build:
>
>
>     ./manage.py <build_id>
>
>
>The build and all related information is deleted from the Toaster
>database.  The deletion operation traverses the ForeignKey relationships
>recursively.
>
>
>
>
>
>On Wed, Mar 19, 2014 at 10:52 AM, Barros Pena, Belen
><belen.barros.pena@intel.com> wrote:
>
>Hi Scott,
>
>There is one more thing that needs to be documented: how to delete builds
>from the Toaster database.
>
>https://bugzilla.yoctoproject.org/show_bug.cgi?id=4625
>
>There is a file in the /poky/bitbake/lib/toaster directory called
>manage.py. You can run that file with additional commands. There are 2
>commands relevant to delete builds:
>
>1. buildslist
>This command is run ./manage.py buildslist and it will show you a
>user-readable tabbed list of build ids and identification information
>
>2. builddelete
>This command is run ./manage.py <build_id> and will delete the build with
>the specified id AND ALL related information (traversing the ForeignKey
>relationships recursively) from the database.
>
>Alex, feel free to add anything that might be missing above.
>
>Since it looks like pretty much everything related to Toaster will be
>documented in the wiki for 1.6, we should probably do the same with this
>one too, but I might add the information to the Toaster manual in the YP
>website as well.
>
>If you have any questions, let us know.
>
>Thanks!
>
>Belén
>
>
>
>On 18/03/2014 16:47, "Barros Pena, Belen" <belen.barros.pena@intel.com>
>wrote:
>
>>Hi Scott,
>>
>>As I mentioned, we would like to document how to set up a Toaster
>>instance
>>in a remote host. Alex Damian sent an email to the mailing list
>>explaining
>>the process back in February. This is it:
>>
>>https://lists.yoctoproject.org/pipermail/toaster/2014-February/000464.htm
>>l
>>
>>We are thinking of documenting this in the wiki for the moment, with
>>maybe
>>a link to it from the existing Toaster section in the Development Manual.
>>
>>Just contact any of us, or the Toaster mailing list, if you have any
>>questions.
>>
>>Thanks for your help with this!
>>
>>Belén
>>
>
>
>>--
>>_______________________________________________
>>toaster mailing list
>>toaster@yoctoproject.org
>>https://lists.yoctoproject.org/listinfo/toaster
>
>
>
>
>
>
>
>
>
>
>
>

Re: Toaster documentation, 1.6 release

[Damian, Alexandru]

[-- Attachment #1: Type: text/plain, Size: 2246 bytes --]

This is a good explanation of the process, thank you.

Alex


On Wed, Mar 19, 2014 at 4:52 PM, Barros Pena, Belen <
belen.barros.pena@intel.com> wrote:

> Hi Scott,
>
> There is one more thing that needs to be documented: how to delete builds
> from the Toaster database.
>
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=4625
>
> There is a file in the /poky/bitbake/lib/toaster directory called
> manage.py. You can run that file with additional commands. There are 2
> commands relevant to delete builds:
>
> 1. buildslist
> This command is run ./manage.py buildslist and it will show you a
> user-readable tabbed list of build ids and identification information
>
> 2. builddelete
> This command is run ./manage.py <build_id> and will delete the build with
> the specified id AND ALL related information (traversing the ForeignKey
> relationships recursively) from the database.
>
> Alex, feel free to add anything that might be missing above.
>
> Since it looks like pretty much everything related to Toaster will be
> documented in the wiki for 1.6, we should probably do the same with this
> one too, but I might add the information to the Toaster manual in the YP
> website as well.
>
> If you have any questions, let us know.
>
> Thanks!
>
> Belén
>
>
>
> On 18/03/2014 16:47, "Barros Pena, Belen" <belen.barros.pena@intel.com>
> wrote:
>
> >Hi Scott,
> >
> >As I mentioned, we would like to document how to set up a Toaster instance
> >in a remote host. Alex Damian sent an email to the mailing list explaining
> >the process back in February. This is it:
> >
> >
> https://lists.yoctoproject.org/pipermail/toaster/2014-February/000464.html
> >
> >We are thinking of documenting this in the wiki for the moment, with maybe
> >a link to it from the existing Toaster section in the Development Manual.
> >
> >Just contact any of us, or the Toaster mailing list, if you have any
> >questions.
> >
> >Thanks for your help with this!
> >
> >Belén
> >
> >--
> >_______________________________________________
> >toaster mailing list
> >toaster@yoctoproject.org
> >https://lists.yoctoproject.org/listinfo/toaster
>
>


-- 
Alex Damian
Yocto Project
SSG / OTC

[-- Attachment #2: Type: text/html, Size: 3458 bytes --]

Re: Toaster documentation, 1.6 release

[Scott Rifenbark]

[-- Attachment #1: Type: text/plain, Size: 2561 bytes --]

Thanks... Not sure if you want me to integrate it into the Toaster section
of the development manual for 1.6?

Scott


On Thu, Mar 20, 2014 at 4:44 AM, Damian, Alexandru <
alexandru.damian@intel.com> wrote:

> This is a good explanation of the process, thank you.
>
> Alex
>
>
> On Wed, Mar 19, 2014 at 4:52 PM, Barros Pena, Belen <
> belen.barros.pena@intel.com> wrote:
>
>> Hi Scott,
>>
>> There is one more thing that needs to be documented: how to delete builds
>> from the Toaster database.
>>
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=4625
>>
>> There is a file in the /poky/bitbake/lib/toaster directory called
>> manage.py. You can run that file with additional commands. There are 2
>> commands relevant to delete builds:
>>
>> 1. buildslist
>> This command is run ./manage.py buildslist and it will show you a
>> user-readable tabbed list of build ids and identification information
>>
>> 2. builddelete
>> This command is run ./manage.py <build_id> and will delete the build with
>> the specified id AND ALL related information (traversing the ForeignKey
>> relationships recursively) from the database.
>>
>> Alex, feel free to add anything that might be missing above.
>>
>> Since it looks like pretty much everything related to Toaster will be
>> documented in the wiki for 1.6, we should probably do the same with this
>> one too, but I might add the information to the Toaster manual in the YP
>> website as well.
>>
>> If you have any questions, let us know.
>>
>> Thanks!
>>
>> Belén
>>
>>
>>
>> On 18/03/2014 16:47, "Barros Pena, Belen" <belen.barros.pena@intel.com>
>> wrote:
>>
>> >Hi Scott,
>> >
>> >As I mentioned, we would like to document how to set up a Toaster
>> instance
>> >in a remote host. Alex Damian sent an email to the mailing list
>> explaining
>> >the process back in February. This is it:
>> >
>> >
>> https://lists.yoctoproject.org/pipermail/toaster/2014-February/000464.html
>> >
>> >We are thinking of documenting this in the wiki for the moment, with
>> maybe
>> >a link to it from the existing Toaster section in the Development Manual.
>> >
>> >Just contact any of us, or the Toaster mailing list, if you have any
>> >questions.
>> >
>> >Thanks for your help with this!
>> >
>> >Belén
>> >
>> >--
>> >_______________________________________________
>> >toaster mailing list
>> >toaster@yoctoproject.org
>> >https://lists.yoctoproject.org/listinfo/toaster
>>
>>
>
>
> --
> Alex Damian
> Yocto Project
> SSG / OTC
>

[-- Attachment #2: Type: text/html, Size: 4093 bytes --]

Re: Toaster documentation, 1.6 release

[Barros Pena, Belen]

On 20/03/2014 11:09, "Scott Rifenbark" <srifenbark@gmail.com> wrote:

>Thanks... Not sure if you want me to integrate it into the Toaster
>section of the development manual for 1.6?

What about adding it to the wiki, like all other stuff for this release,
with a link to it in the dev manual?

>
>Scott
>
>
>
>On Thu, Mar 20, 2014 at 4:44 AM, Damian, Alexandru
><alexandru.damian@intel.com> wrote:
>
>This is a good explanation of the process, thank you.
>
>
>Alex
>
>
>
>On Wed, Mar 19, 2014 at 4:52 PM, Barros Pena, Belen
><belen.barros.pena@intel.com> wrote:
>
>Hi Scott,
>
>There is one more thing that needs to be documented: how to delete builds
>from the Toaster database.
>
>https://bugzilla.yoctoproject.org/show_bug.cgi?id=4625
>
>There is a file in the /poky/bitbake/lib/toaster directory called
>manage.py. You can run that file with additional commands. There are 2
>commands relevant to delete builds:
>
>1. buildslist
>This command is run ./manage.py buildslist and it will show you a
>user-readable tabbed list of build ids and identification information
>
>2. builddelete
>This command is run ./manage.py <build_id> and will delete the build with
>the specified id AND ALL related information (traversing the ForeignKey
>relationships recursively) from the database.
>
>Alex, feel free to add anything that might be missing above.
>
>Since it looks like pretty much everything related to Toaster will be
>documented in the wiki for 1.6, we should probably do the same with this
>one too, but I might add the information to the Toaster manual in the YP
>website as well.
>
>If you have any questions, let us know.
>
>Thanks!
>
>Belén
>
>
>
>On 18/03/2014 16:47, "Barros Pena, Belen" <belen.barros.pena@intel.com>
>wrote:
>
>>Hi Scott,
>>
>>As I mentioned, we would like to document how to set up a Toaster
>>instance
>>in a remote host. Alex Damian sent an email to the mailing list
>>explaining
>>the process back in February. This is it:
>>
>>https://lists.yoctoproject.org/pipermail/toaster/2014-February/000464.htm
>>l
>>
>>We are thinking of documenting this in the wiki for the moment, with
>>maybe
>>a link to it from the existing Toaster section in the Development Manual.
>>
>>Just contact any of us, or the Toaster mailing list, if you have any
>>questions.
>>
>>Thanks for your help with this!
>>
>>Belén
>>
>
>
>>--
>>_______________________________________________
>>toaster mailing list
>>toaster@yoctoproject.org
>>https://lists.yoctoproject.org/listinfo/toaster
>
>
>
>
>
>
>
>
>
>
>-- 
>Alex Damian
>Yocto Project
>
>SSG / OTC 
>
>
>
>
>
>
>

Re: Toaster documentation, 1.6 release

[Scott Rifenbark]

[-- Attachment #1: Type: text/plain, Size: 3950 bytes --]

Belen,

Here is the text that references the wiki from the Toaster section.  Right
now it is going to a specific section in the wiki.  Depending on how you
change the wiki I may or may not have to update the text.  Just let me know
when the wiki has settled out with the inclusion of this new information
and I will adjust/or not adjust the manual's reference text.

Scott (section follows)

The remainder of this section describes what you need to have in place to
use Toaster, how to start it, use it, and stop it. For additional
information on installing and running Toaster, see the "Installation and
Running<https://wiki.yoctoproject.org/wiki/Toaster#Installation_and_Running>"
section of the "Toaster" wiki page. For complete information on the API and
its search operation URI, parameters, and responses, see the REST API
Contracts <https://wiki.yoctoproject.org/wiki/REST_API_Contracts> Wiki
page.


On Thu, Mar 20, 2014 at 5:30 AM, Barros Pena, Belen <
belen.barros.pena@intel.com> wrote:

>
> On 20/03/2014 11:09, "Scott Rifenbark" <srifenbark@gmail.com> wrote:
>
> >Thanks... Not sure if you want me to integrate it into the Toaster
> >section of the development manual for 1.6?
>
> What about adding it to the wiki, like all other stuff for this release,
> with a link to it in the dev manual?
>
> >
> >Scott
> >
> >
> >
> >On Thu, Mar 20, 2014 at 4:44 AM, Damian, Alexandru
> ><alexandru.damian@intel.com> wrote:
> >
> >This is a good explanation of the process, thank you.
> >
> >
> >Alex
> >
> >
> >
> >On Wed, Mar 19, 2014 at 4:52 PM, Barros Pena, Belen
> ><belen.barros.pena@intel.com> wrote:
> >
> >Hi Scott,
> >
> >There is one more thing that needs to be documented: how to delete builds
> >from the Toaster database.
> >
> >https://bugzilla.yoctoproject.org/show_bug.cgi?id=4625
> >
> >There is a file in the /poky/bitbake/lib/toaster directory called
> >manage.py. You can run that file with additional commands. There are 2
> >commands relevant to delete builds:
> >
> >1. buildslist
> >This command is run ./manage.py buildslist and it will show you a
> >user-readable tabbed list of build ids and identification information
> >
> >2. builddelete
> >This command is run ./manage.py <build_id> and will delete the build with
> >the specified id AND ALL related information (traversing the ForeignKey
> >relationships recursively) from the database.
> >
> >Alex, feel free to add anything that might be missing above.
> >
> >Since it looks like pretty much everything related to Toaster will be
> >documented in the wiki for 1.6, we should probably do the same with this
> >one too, but I might add the information to the Toaster manual in the YP
> >website as well.
> >
> >If you have any questions, let us know.
> >
> >Thanks!
> >
> >Belén
> >
> >
> >
> >On 18/03/2014 16:47, "Barros Pena, Belen" <belen.barros.pena@intel.com>
> >wrote:
> >
> >>Hi Scott,
> >>
> >>As I mentioned, we would like to document how to set up a Toaster
> >>instance
> >>in a remote host. Alex Damian sent an email to the mailing list
> >>explaining
> >>the process back in February. This is it:
> >>
> >>
> https://lists.yoctoproject.org/pipermail/toaster/2014-February/000464.htm
> >>l
> >>
> >>We are thinking of documenting this in the wiki for the moment, with
> >>maybe
> >>a link to it from the existing Toaster section in the Development Manual.
> >>
> >>Just contact any of us, or the Toaster mailing list, if you have any
> >>questions.
> >>
> >>Thanks for your help with this!
> >>
> >>Belén
> >>
> >
> >
> >>--
> >>_______________________________________________
> >>toaster mailing list
> >>toaster@yoctoproject.org
> >>https://lists.yoctoproject.org/listinfo/toaster
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >--
> >Alex Damian
> >Yocto Project
> >
> >SSG / OTC
> >
> >
> >
> >
> >
> >
> >
>
>

[-- Attachment #2: Type: text/html, Size: 5727 bytes --]

Re: Toaster documentation, 1.6 release

[Barros Pena, Belen]

Hi Scott, 

There is some more detail we need to add to the explanation about how to
delete builds from the Toaster database. This is Alex's explanation:

The buildslist and builddelete ​commands ​have some prerequisites in terms
of how they're invoked:

* in the default configuration, the current working directory needs ​to be
the 'build/' directory as to let the system find the "toaster.sqlite" file
in this directory

* in other database configuration, it may be possible to invoke from other
directories, provided that the toastermain/settings.py file is correctly
configured as to point to the correct database backend.

I recommend to always call manage.py from the "build/" directory.

Thanks!

Belén



On 19/03/2014 21:55, "Scott Rifenbark" <srifenbark@gmail.com> wrote:

>Here is a quick section on deleting a build from the toaster database.
>
>-----------------------------------
>
>Deleting a Build from the Toaster Database
>
>
>You can use the manage.py command, which is located in the
>/poky/bitbake/lib/toaster directory to identify and delete builds from
>the Toaster database.  Follow these steps to delete a build:
>
>
>1. Identify the build:  Run the following command from the toaster
>directory to display a user-readable, tabbed list of build IDs and
>identification information:
>
>
>     ./manage.py buildslist
>
>
>2. Delete a specific build: Using the build ID displayed in the previous
>step, run the following command to delete a specific build:
>
>
>     ./manage.py <build_id>
>
>
>The build and all related information is deleted from the Toaster
>database.  The deletion operation traverses the ForeignKey relationships
>recursively.
>
>
>
>
>
>On Wed, Mar 19, 2014 at 10:52 AM, Barros Pena, Belen
><belen.barros.pena@intel.com> wrote:
>
>Hi Scott,
>
>There is one more thing that needs to be documented: how to delete builds
>from the Toaster database.
>
>https://bugzilla.yoctoproject.org/show_bug.cgi?id=4625
>
>There is a file in the /poky/bitbake/lib/toaster directory called
>manage.py. You can run that file with additional commands. There are 2
>commands relevant to delete builds:
>
>1. buildslist
>This command is run ./manage.py buildslist and it will show you a
>user-readable tabbed list of build ids and identification information
>
>2. builddelete
>This command is run ./manage.py <build_id> and will delete the build with
>the specified id AND ALL related information (traversing the ForeignKey
>relationships recursively) from the database.
>
>Alex, feel free to add anything that might be missing above.
>
>Since it looks like pretty much everything related to Toaster will be
>documented in the wiki for 1.6, we should probably do the same with this
>one too, but I might add the information to the Toaster manual in the YP
>website as well.
>
>If you have any questions, let us know.
>
>Thanks!
>
>Belén
>
>
>
>On 18/03/2014 16:47, "Barros Pena, Belen" <belen.barros.pena@intel.com>
>wrote:
>
>>Hi Scott,
>>
>>As I mentioned, we would like to document how to set up a Toaster
>>instance
>>in a remote host. Alex Damian sent an email to the mailing list
>>explaining
>>the process back in February. This is it:
>>
>>https://lists.yoctoproject.org/pipermail/toaster/2014-February/000464.htm
>>l
>>
>>We are thinking of documenting this in the wiki for the moment, with
>>maybe
>>a link to it from the existing Toaster section in the Development Manual.
>>
>>Just contact any of us, or the Toaster mailing list, if you have any
>>questions.
>>
>>Thanks for your help with this!
>>
>>Belén
>>
>
>
>>--
>>_______________________________________________
>>toaster mailing list
>>toaster@yoctoproject.org
>>https://lists.yoctoproject.org/listinfo/toaster
>
>
>
>
>
>
>
>
>
>
>
>

Re: Toaster documentation, 1.6 release

[Scott Rifenbark]

[-- Attachment #1: Type: text/plain, Size: 6067 bytes --]

Hi Belen,

Here is a re-written version.  I did not know how to cast that very last
sentence.  It seemed to come from nowhere.  The piece talks about two
commands, the build directory and two files (toaster.sqlite and
toastermain/setting.py).  The manage.py thing comes out of the blue.  So, I
just put it at the end.  I imagine there is some relationship between it
and the rest of the information.  If I knew the relationship I could work
it into the main stuff a little better.

Also, I am not sure if the "build/" directory means literally the default
build directory, which is named "build", or if it means the build directory
in a general sense, which could be named I suppose whatever the user wants
it to be named.

Finally, I am not mentioning the words "pre-requisites" or "requirements"
in the re-write even though the original text cast the information as
such.  Really, what is here doesn't qualify as per-requisites.  They are
more like "behaviors".

Hope this helps.  Let me know if you need further work on it.

Scott

=============================================

When using the buildslist and builddelete commands, you need to consider
the following:

* For default configurations, your working directory must be the "build"
directory.  Using these command from the "build" directory allows Toaster
to find the "toaster.sqlite" file, which is located in the "build"
directory.

* For other database configurations, it is possible that you can use these
commands from a directory other than the "build" directory.  To do so, the
"toastermain/settings.py" file must be configured to point to the correct
database backend.

It is recommended to always call "manage.py" from the "build" directory.

==========================================================


On Wed, Mar 26, 2014 at 5:23 AM, Barros Pena, Belen <
belen.barros.pena@intel.com> wrote:

> Hi Scott,
>
> There is some more detail we need to add to the explanation about how to
> delete builds from the Toaster database. This is Alex's explanation:
>
> The buildslist and builddelete commands have some prerequisites in terms
> of how they're invoked:
>
> * in the default configuration, the current working directory needs to be
> the 'build/' directory as to let the system find the "toaster.sqlite" file
> in this directory
>
> * in other database configuration, it may be possible to invoke from other
> directories, provided that the toastermain/settings.py file is correctly
> configured as to point to the correct database backend.
>
> I recommend to always call manage.py from the "build/" directory.
>
> Thanks!
>
> Belén
>
>
>
> On 19/03/2014 21:55, "Scott Rifenbark" <srifenbark@gmail.com> wrote:
>
> >Here is a quick section on deleting a build from the toaster database.
> >
> >-----------------------------------
> >
> >Deleting a Build from the Toaster Database
> >
> >
> >You can use the manage.py command, which is located in the
> >/poky/bitbake/lib/toaster directory to identify and delete builds from
> >the Toaster database.  Follow these steps to delete a build:
> >
> >
> >1. Identify the build:  Run the following command from the toaster
> >directory to display a user-readable, tabbed list of build IDs and
> >identification information:
> >
> >
> >     ./manage.py buildslist
> >
> >
> >2. Delete a specific build: Using the build ID displayed in the previous
> >step, run the following command to delete a specific build:
> >
> >
> >     ./manage.py <build_id>
> >
> >
> >The build and all related information is deleted from the Toaster
> >database.  The deletion operation traverses the ForeignKey relationships
> >recursively.
> >
> >
> >
> >
> >
> >On Wed, Mar 19, 2014 at 10:52 AM, Barros Pena, Belen
> ><belen.barros.pena@intel.com> wrote:
> >
> >Hi Scott,
> >
> >There is one more thing that needs to be documented: how to delete builds
> >from the Toaster database.
> >
> >https://bugzilla.yoctoproject.org/show_bug.cgi?id=4625
> >
> >There is a file in the /poky/bitbake/lib/toaster directory called
> >manage.py. You can run that file with additional commands. There are 2
> >commands relevant to delete builds:
> >
> >1. buildslist
> >This command is run ./manage.py buildslist and it will show you a
> >user-readable tabbed list of build ids and identification information
> >
> >2. builddelete
> >This command is run ./manage.py <build_id> and will delete the build with
> >the specified id AND ALL related information (traversing the ForeignKey
> >relationships recursively) from the database.
> >
> >Alex, feel free to add anything that might be missing above.
> >
> >Since it looks like pretty much everything related to Toaster will be
> >documented in the wiki for 1.6, we should probably do the same with this
> >one too, but I might add the information to the Toaster manual in the YP
> >website as well.
> >
> >If you have any questions, let us know.
> >
> >Thanks!
> >
> >Belén
> >
> >
> >
> >On 18/03/2014 16:47, "Barros Pena, Belen" <belen.barros.pena@intel.com>
> >wrote:
> >
> >>Hi Scott,
> >>
> >>As I mentioned, we would like to document how to set up a Toaster
> >>instance
> >>in a remote host. Alex Damian sent an email to the mailing list
> >>explaining
> >>the process back in February. This is it:
> >>
> >>
> https://lists.yoctoproject.org/pipermail/toaster/2014-February/000464.htm
> >>l
> >>
> >>We are thinking of documenting this in the wiki for the moment, with
> >>maybe
> >>a link to it from the existing Toaster section in the Development Manual.
> >>
> >>Just contact any of us, or the Toaster mailing list, if you have any
> >>questions.
> >>
> >>Thanks for your help with this!
> >>
> >>Belén
> >>
> >
> >
> >>--
> >>_______________________________________________
> >>toaster mailing list
> >>toaster@yoctoproject.org
> >>https://lists.yoctoproject.org/listinfo/toaster
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>

[-- Attachment #2: Type: text/html, Size: 8063 bytes --]

Re: Toaster documentation, 1.6 release

[Barros Pena, Belen]

Thanks, Scott. Alex should review it when he has a chance.

Cheers

Belén

On 26/03/2014 12:31, "Scott Rifenbark" <srifenbark@gmail.com> wrote:

>Hi Belen,
>
>
>Here is a re-written version.  I did not know how to cast that very last
>sentence.  It seemed to come from nowhere.  The piece talks about two
>commands, the build directory and two files (toaster.sqlite and
>toastermain/setting.py).  The manage.py thing comes
> out of the blue.  So, I just put it at the end.  I imagine there is some
>relationship between it and the rest of the information.  If I knew the
>relationship I could work it into the main stuff a little better.
>
>
>
>Also, I am not sure if the "build/" directory means literally the default
>build directory, which is named "build", or if it means the build
>directory in a general sense, which could be named I suppose whatever the
>user wants it to be named.
>
>
>Finally, I am not mentioning the words "pre-requisites" or "requirements"
>in the re-write even though the original text cast the information as
>such.  Really, what is here doesn't qualify as per-requisites.  They are
>more like "behaviors".
>
>
>Hope this helps.  Let me know if you need further work on it.
>
>
>Scott
>
>
>=============================================
>
>
>When using the buildslist and builddelete commands, you need to consider
>the following:
>
>
>* For default configurations, your working directory must be the "build"
>directory.  Using these command from the "build" directory allows Toaster
>to find the "toaster.sqlite" file, which is located in the "build"
>directory.
>
>
>* For other database configurations, it is possible that you can use
>these commands from a directory other than the "build" directory.  To do
>so, the "toastermain/settings.py" file must be configured to point to the
>correct database backend.
>
>
>It is recommended to always call "manage.py" from the "build" directory.
>
>==========================================================
>
>
>On Wed, Mar 26, 2014 at 5:23 AM, Barros Pena, Belen
><belen.barros.pena@intel.com> wrote:
>
>Hi Scott,
>
>There is some more detail we need to add to the explanation about how to
>delete builds from the Toaster database. This is Alex's explanation:
>
>The buildslist and builddelete commands have some prerequisites in terms
>of how they're invoked:
>
>* in the default configuration, the current working directory needs to be
>the 'build/' directory as to let the system find the "toaster.sqlite" file
>in this directory
>
>* in other database configuration, it may be possible to invoke from other
>directories, provided that the toastermain/settings.py file is correctly
>configured as to point to the correct database backend.
>
>I recommend to always call manage.py from the "build/" directory.
>
>Thanks!
>
>Belén
>
>
>
>On 19/03/2014 21:55, "Scott Rifenbark" <srifenbark@gmail.com> wrote:
>
>
>>Here is a quick section on deleting a build from the toaster database.
>>
>>-----------------------------------
>>
>>Deleting a Build from the Toaster Database
>>
>>
>>You can use the manage.py command, which is located in the
>>/poky/bitbake/lib/toaster directory to identify and delete builds from
>>the Toaster database.  Follow these steps to delete a build:
>>
>>
>>1. Identify the build:  Run the following command from the toaster
>>directory to display a user-readable, tabbed list of build IDs and
>>identification information:
>>
>>
>>     ./manage.py buildslist
>>
>>
>>2. Delete a specific build: Using the build ID displayed in the previous
>>step, run the following command to delete a specific build:
>>
>>
>>     ./manage.py <build_id>
>>
>>
>>The build and all related information is deleted from the Toaster
>>database.  The deletion operation traverses the ForeignKey relationships
>>recursively.
>>
>>
>>
>>
>>
>>On Wed, Mar 19, 2014 at 10:52 AM, Barros Pena, Belen
>><belen.barros.pena@intel.com> wrote:
>>
>>Hi Scott,
>>
>>There is one more thing that needs to be documented: how to delete builds
>>from the Toaster database.
>>
>>https://bugzilla.yoctoproject.org/show_bug.cgi?id=4625
>>
>>There is a file in the /poky/bitbake/lib/toaster directory called
>>manage.py. You can run that file with additional commands. There are 2
>>commands relevant to delete builds:
>>
>>1. buildslist
>>This command is run ./manage.py buildslist and it will show you a
>>user-readable tabbed list of build ids and identification information
>>
>>2. builddelete
>>This command is run ./manage.py <build_id> and will delete the build with
>>the specified id AND ALL related information (traversing the ForeignKey
>>relationships recursively) from the database.
>>
>>Alex, feel free to add anything that might be missing above.
>>
>>Since it looks like pretty much everything related to Toaster will be
>>documented in the wiki for 1.6, we should probably do the same with this
>>one too, but I might add the information to the Toaster manual in the YP
>>website as well.
>>
>>If you have any questions, let us know.
>>
>>Thanks!
>>
>>Belén
>>
>>
>>
>>On 18/03/2014 16:47, "Barros Pena, Belen" <belen.barros.pena@intel.com>
>>wrote:
>>
>>>Hi Scott,
>>>
>>>As I mentioned, we would like to document how to set up a Toaster
>>>instance
>>>in a remote host. Alex Damian sent an email to the mailing list
>>>explaining
>>>the process back in February. This is it:
>>>
>>>https://lists.yoctoproject.org/pipermail/toaster/2014-February/000464.ht
>>>m
>>>l
>>>
>>>We are thinking of documenting this in the wiki for the moment, with
>>>maybe
>>>a link to it from the existing Toaster section in the Development
>>>Manual.
>>>
>>>Just contact any of us, or the Toaster mailing list, if you have any
>>>questions.
>>>
>>>Thanks for your help with this!
>>>
>>>Belén
>>>
>>
>>
>>>--
>>>_______________________________________________
>>>toaster mailing list
>>>toaster@yoctoproject.org
>>>https://lists.yoctoproject.org/listinfo/toaster
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

Re: Toaster documentation, 1.6 release

[Damian, Alexandru]

[-- Attachment #1: Type: text/plain, Size: 7462 bytes --]

This version is clear and explicit for me. But I understand that this may
be a bit confusing for some users.

I have more comments below, for Scott's concerns.

Thank you, guys!
Alex


On Thu, Mar 27, 2014 at 10:30 AM, Barros Pena, Belen <
belen.barros.pena@intel.com> wrote:

> Thanks, Scott. Alex should review it when he has a chance.
>
> Cheers
>
> Belén
>
> On 26/03/2014 12:31, "Scott Rifenbark" <srifenbark@gmail.com> wrote:
>
> >Hi Belen,
> >
> >
> >Here is a re-written version.  I did not know how to cast that very last
> >sentence.  It seemed to come from nowhere.  The piece talks about two
> >commands, the build directory and two files (toaster.sqlite and
> >toastermain/setting.py).  The manage.py thing comes
> > out of the blue.  So, I just put it at the end.  I imagine there is some
> >relationship between it and the rest of the information.  If I knew the
> >relationship I could work it into the main stuff a little better.
>

​
[Alex]
manage.py is ​referring to this file in the tree:
bitbake/lib/toaster/manage.py
It's the main Django control script in the toaster project. Maybe we should
make this clear, and spell out the entire name ?

 >
> >
> >
> >Also, I am not sure if the "build/" directory means literally the default
> >build directory, which is named "build", or if it means the build
>

​[Alex] It's ​

​the build directory in the general sense, I assumed that the users
don't change this name, hence the 'build/' reference. How is it called in
other
pieces of documentation ?

​

> >directory in a general sense, which could be named I suppose whatever the
> >user wants it to be named.
> >
> >
> >Finally, I am not mentioning the words "pre-requisites" or "requirements"
> >in the re-write even though the original text cast the information as
> >such.  Really, what is here doesn't qualify as per-requisites.  They are
> >more like "behaviors".
> >
> >
> >Hope this helps.  Let me know if you need further work on it.
> >
> >
> >Scott
> >
> >
> >=============================================
> >
> >
> >When using the buildslist and builddelete commands, you need to consider
> >the following:
> >
> >
> >* For default configurations, your working directory must be the "build"
> >directory.  Using these command from the "build" directory allows Toaster
> >to find the "toaster.sqlite" file, which is located in the "build"
> >directory.
> >
> >
> >* For other database configurations, it is possible that you can use
> >these commands from a directory other than the "build" directory.  To do
> >so, the "toastermain/settings.py" file must be configured to point to the
> >correct database backend.
> >
> >
> >It is recommended to always call "manage.py" from the "build" directory.
> >
> >==========================================================
> >
> >
> >On Wed, Mar 26, 2014 at 5:23 AM, Barros Pena, Belen
> ><belen.barros.pena@intel.com> wrote:
> >
> >Hi Scott,
> >
> >There is some more detail we need to add to the explanation about how to
> >delete builds from the Toaster database. This is Alex's explanation:
> >
> >The buildslist and builddelete commands have some prerequisites in terms
> >of how they're invoked:
> >
> >* in the default configuration, the current working directory needs to be
> >the 'build/' directory as to let the system find the "toaster.sqlite" file
> >in this directory
> >
> >* in other database configuration, it may be possible to invoke from other
> >directories, provided that the toastermain/settings.py file is correctly
> >configured as to point to the correct database backend.
> >
> >I recommend to always call manage.py from the "build/" directory.
> >
> >Thanks!
> >
> >Belén
> >
> >
> >
> >On 19/03/2014 21:55, "Scott Rifenbark" <srifenbark@gmail.com> wrote:
> >
> >
> >>Here is a quick section on deleting a build from the toaster database.
> >>
> >>-----------------------------------
> >>
> >>Deleting a Build from the Toaster Database
> >>
> >>
> >>You can use the manage.py command, which is located in the
> >>/poky/bitbake/lib/toaster directory to identify and delete builds from
> >>the Toaster database.  Follow these steps to delete a build:
> >>
> >>
> >>1. Identify the build:  Run the following command from the toaster
> >>directory to display a user-readable, tabbed list of build IDs and
> >>identification information:
> >>
> >>
> >>     ./manage.py buildslist
> >>
> >>
> >>2. Delete a specific build: Using the build ID displayed in the previous
> >>step, run the following command to delete a specific build:
> >>
> >>
> >>     ./manage.py <build_id>
> >>
> >>
> >>The build and all related information is deleted from the Toaster
> >>database.  The deletion operation traverses the ForeignKey relationships
> >>recursively.
> >>
> >>
> >>
> >>
> >>
> >>On Wed, Mar 19, 2014 at 10:52 AM, Barros Pena, Belen
> >><belen.barros.pena@intel.com> wrote:
> >>
> >>Hi Scott,
> >>
> >>There is one more thing that needs to be documented: how to delete builds
> >>from the Toaster database.
> >>
> >>https://bugzilla.yoctoproject.org/show_bug.cgi?id=4625
> >>
> >>There is a file in the /poky/bitbake/lib/toaster directory called
> >>manage.py. You can run that file with additional commands. There are 2
> >>commands relevant to delete builds:
> >>
> >>1. buildslist
> >>This command is run ./manage.py buildslist and it will show you a
> >>user-readable tabbed list of build ids and identification information
> >>
> >>2. builddelete
> >>This command is run ./manage.py <build_id> and will delete the build with
> >>the specified id AND ALL related information (traversing the ForeignKey
> >>relationships recursively) from the database.
> >>
> >>Alex, feel free to add anything that might be missing above.
> >>
> >>Since it looks like pretty much everything related to Toaster will be
> >>documented in the wiki for 1.6, we should probably do the same with this
> >>one too, but I might add the information to the Toaster manual in the YP
> >>website as well.
> >>
> >>If you have any questions, let us know.
> >>
> >>Thanks!
> >>
> >>Belén
> >>
> >>
> >>
> >>On 18/03/2014 16:47, "Barros Pena, Belen" <belen.barros.pena@intel.com>
> >>wrote:
> >>
> >>>Hi Scott,
> >>>
> >>>As I mentioned, we would like to document how to set up a Toaster
> >>>instance
> >>>in a remote host. Alex Damian sent an email to the mailing list
> >>>explaining
> >>>the process back in February. This is it:
> >>>
> >>>
> https://lists.yoctoproject.org/pipermail/toaster/2014-February/000464.ht
> >>>m
> >>>l
> >>>
> >>>We are thinking of documenting this in the wiki for the moment, with
> >>>maybe
> >>>a link to it from the existing Toaster section in the Development
> >>>Manual.
> >>>
> >>>Just contact any of us, or the Toaster mailing list, if you have any
> >>>questions.
> >>>
> >>>Thanks for your help with this!
> >>>
> >>>Belén
> >>>
> >>
> >>
> >>>--
> >>>_______________________________________________
> >>>toaster mailing list
> >>>toaster@yoctoproject.org
> >>>https://lists.yoctoproject.org/listinfo/toaster
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>


-- 
Alex Damian
Yocto Project
SSG / OTC

[-- Attachment #2: Type: text/html, Size: 11485 bytes --]

Re: Toaster documentation, 1.6 release

[Scott Rifenbark]

[-- Attachment #1: Type: text/plain, Size: 8668 bytes --]

On Mon, Mar 31, 2014 at 11:01 AM, Damian, Alexandru <
alexandru.damian@intel.com> wrote:

> This version is clear and explicit for me. But I understand that this may
> be a bit confusing for some users.
>
> I have more comments below, for Scott's concerns.
>
> Thank you, guys!
> Alex
>
>
> On Thu, Mar 27, 2014 at 10:30 AM, Barros Pena, Belen <
> belen.barros.pena@intel.com> wrote:
>
>> Thanks, Scott. Alex should review it when he has a chance.
>>
>> Cheers
>>
>> Belén
>>
>> On 26/03/2014 12:31, "Scott Rifenbark" <srifenbark@gmail.com> wrote:
>>
>> >Hi Belen,
>> >
>> >
>> >Here is a re-written version.  I did not know how to cast that very last
>> >sentence.  It seemed to come from nowhere.  The piece talks about two
>> >commands, the build directory and two files (toaster.sqlite and
>> >toastermain/setting.py).  The manage.py thing comes
>> > out of the blue.  So, I just put it at the end.  I imagine there is some
>> >relationship between it and the rest of the information.  If I knew the
>> >relationship I could work it into the main stuff a little better.
>>
>
> 
> [Alex]
> manage.py is referring to this file in the tree:
> bitbake/lib/toaster/manage.py
> It's the main Django control script in the toaster project. Maybe we should
> make this clear, and spell out the entire name ?
>

Alex - I would use the full path name just to be clear about that manage.py
file.


>
>  >
>> >
>> >
>> >Also, I am not sure if the "build/" directory means literally the default
>> >build directory, which is named "build", or if it means the build
>>
>
> [Alex] It's 
>
> the build directory in the general sense, I assumed that the users
> don't change this name, hence the 'build/' reference. How is it called in
> other
> pieces of documentation ?
>

Alex - in the mainstream YP documentation, the build directory is
consistently referred to as "Build Directory."  When I use the term in a
chapter or section I try to link the term to the formal definition in the
dev-manual.  I don't link every occurrence but the first ones to appear in
major sections or chapters.  The link is
http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#build-directory.
When I am referring to an actual Build Directory, I format it using a
different font (Courier) and use the actual name.  So, if it is the default
Build Directory, I say the build directory, and the word "build" appears in
the font reserved for filenames and commands throughout the YP
documentation.

>
> 
>
>> >directory in a general sense, which could be named I suppose whatever the
>> >user wants it to be named.
>> >
>> >
>> >Finally, I am not mentioning the words "pre-requisites" or "requirements"
>> >in the re-write even though the original text cast the information as
>> >such.  Really, what is here doesn't qualify as per-requisites.  They are
>> >more like "behaviors".
>> >
>> >
>> >Hope this helps.  Let me know if you need further work on it.
>> >
>> >
>> >Scott
>> >
>> >
>> >=============================================
>> >
>> >
>> >When using the buildslist and builddelete commands, you need to consider
>> >the following:
>> >
>> >
>> >* For default configurations, your working directory must be the "build"
>> >directory.  Using these command from the "build" directory allows Toaster
>> >to find the "toaster.sqlite" file, which is located in the "build"
>> >directory.
>> >
>> >
>> >* For other database configurations, it is possible that you can use
>> >these commands from a directory other than the "build" directory.  To do
>> >so, the "toastermain/settings.py" file must be configured to point to the
>> >correct database backend.
>> >
>> >
>> >It is recommended to always call "manage.py" from the "build" directory.
>> >
>> >==========================================================
>> >
>> >
>> >On Wed, Mar 26, 2014 at 5:23 AM, Barros Pena, Belen
>> ><belen.barros.pena@intel.com> wrote:
>> >
>> >Hi Scott,
>> >
>> >There is some more detail we need to add to the explanation about how to
>> >delete builds from the Toaster database. This is Alex's explanation:
>> >
>> >The buildslist and builddelete commands have some prerequisites in terms
>> >of how they're invoked:
>> >
>> >* in the default configuration, the current working directory needs to be
>> >the 'build/' directory as to let the system find the "toaster.sqlite"
>> file
>> >in this directory
>> >
>> >* in other database configuration, it may be possible to invoke from
>> other
>> >directories, provided that the toastermain/settings.py file is correctly
>> >configured as to point to the correct database backend.
>> >
>> >I recommend to always call manage.py from the "build/" directory.
>> >
>> >Thanks!
>> >
>> >Belén
>> >
>> >
>> >
>> >On 19/03/2014 21:55, "Scott Rifenbark" <srifenbark@gmail.com> wrote:
>> >
>> >
>> >>Here is a quick section on deleting a build from the toaster database.
>> >>
>> >>-----------------------------------
>> >>
>> >>Deleting a Build from the Toaster Database
>> >>
>> >>
>> >>You can use the manage.py command, which is located in the
>> >>/poky/bitbake/lib/toaster directory to identify and delete builds from
>> >>the Toaster database.  Follow these steps to delete a build:
>> >>
>> >>
>> >>1. Identify the build:  Run the following command from the toaster
>> >>directory to display a user-readable, tabbed list of build IDs and
>> >>identification information:
>> >>
>> >>
>> >>     ./manage.py buildslist
>> >>
>> >>
>> >>2. Delete a specific build: Using the build ID displayed in the previous
>> >>step, run the following command to delete a specific build:
>> >>
>> >>
>> >>     ./manage.py <build_id>
>> >>
>> >>
>> >>The build and all related information is deleted from the Toaster
>> >>database.  The deletion operation traverses the ForeignKey relationships
>> >>recursively.
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>On Wed, Mar 19, 2014 at 10:52 AM, Barros Pena, Belen
>> >><belen.barros.pena@intel.com> wrote:
>> >>
>> >>Hi Scott,
>> >>
>> >>There is one more thing that needs to be documented: how to delete
>> builds
>> >>from the Toaster database.
>> >>
>> >>https://bugzilla.yoctoproject.org/show_bug.cgi?id=4625
>> >>
>> >>There is a file in the /poky/bitbake/lib/toaster directory called
>> >>manage.py. You can run that file with additional commands. There are 2
>> >>commands relevant to delete builds:
>> >>
>> >>1. buildslist
>> >>This command is run ./manage.py buildslist and it will show you a
>> >>user-readable tabbed list of build ids and identification information
>> >>
>> >>2. builddelete
>> >>This command is run ./manage.py <build_id> and will delete the build
>> with
>> >>the specified id AND ALL related information (traversing the ForeignKey
>> >>relationships recursively) from the database.
>> >>
>> >>Alex, feel free to add anything that might be missing above.
>> >>
>> >>Since it looks like pretty much everything related to Toaster will be
>> >>documented in the wiki for 1.6, we should probably do the same with this
>> >>one too, but I might add the information to the Toaster manual in the YP
>> >>website as well.
>> >>
>> >>If you have any questions, let us know.
>> >>
>> >>Thanks!
>> >>
>> >>Belén
>> >>
>> >>
>> >>
>> >>On 18/03/2014 16:47, "Barros Pena, Belen" <belen.barros.pena@intel.com>
>> >>wrote:
>> >>
>> >>>Hi Scott,
>> >>>
>> >>>As I mentioned, we would like to document how to set up a Toaster
>> >>>instance
>> >>>in a remote host. Alex Damian sent an email to the mailing list
>> >>>explaining
>> >>>the process back in February. This is it:
>> >>>
>> >>>
>> https://lists.yoctoproject.org/pipermail/toaster/2014-February/000464.ht
>> >>>m
>> >>>l
>> >>>
>> >>>We are thinking of documenting this in the wiki for the moment, with
>> >>>maybe
>> >>>a link to it from the existing Toaster section in the Development
>> >>>Manual.
>> >>>
>> >>>Just contact any of us, or the Toaster mailing list, if you have any
>> >>>questions.
>> >>>
>> >>>Thanks for your help with this!
>> >>>
>> >>>Belén
>> >>>
>> >>
>> >>
>> >>>--
>> >>>_______________________________________________
>> >>>toaster mailing list
>> >>>toaster@yoctoproject.org
>> >>>https://lists.yoctoproject.org/listinfo/toaster
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>>
>>
>
>
> --
> Alex Damian
> Yocto Project
> SSG / OTC
>

[-- Attachment #2: Type: text/html, Size: 13244 bytes --]

Re: Toaster documentation, 1.6 release

[Damian, Alexandru]

[-- Attachment #1: Type: text/plain, Size: 1900 bytes --]

> Alex - I would use the full path name just to be clear about that
> manage.py file.
>
>
​[Alex] Good idea, thank you.
​


>
> Alex - in the mainstream YP documentation, the build directory is
> consistently referred to as "Build Directory."  When I use the term in a
> chapter or section I try to link the term to the formal definition in the
> dev-manual.  I don't link every occurrence but the first ones to appear in
> major sections or chapters.  The link is
> http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#build-directory.
> When I am referring to an actual Build Directory, I format it using a
> different font (Courier) and use the actual name.  So, if it is the default
> Build Directory, I say the build directory, and the word "build" appears in
> the font reserved for filenames and commands throughout the YP
> documentation.
>
>>
>> ​[Alex] Let's change it then to "Build Directory", I think this conveys
the proper message.​



>  >=============================================
>>> >
>>> >
>>> >When using the buildslist and builddelete commands, you need to consider
>>> >the following:
>>> >
>>> >
>>> >* For default configurations, your working directory must be the "build"
>>> >directory.  Using these command from the "build" directory allows
>>> Toaster
>>> >to find the "toaster.sqlite" file, which is located in the "build"
>>> >directory.
>>> >
>>> >
>>> >* For other database configurations, it is possible that you can use
>>> >these commands from a directory other than the "build" directory.  To do
>>> >so, the "toastermain/settings.py" file must be configured to point to
>>> the
>>> >correct database backend.
>>> >
>>> >
>>> >It is recommended to always call "manage.py" from the "build" directory.
>>> >
>>> >==========================================================
>>> >
>>>
>>

[-- Attachment #2: Type: text/html, Size: 3884 bytes --]

Re: Toaster documentation, 1.6 release

[Barros Pena, Belen]

I have added the content to the wiki:

https://wiki.yoctoproject.org/wiki/Toaster#Deleting_a_Build_from_the_Toaste
r_Database

Feel free to update as needed.

Cheers

Belén

On 01/04/2014 07:45, "Damian, Alexandru" <alexandru.damian@intel.com>
wrote:

>
>
>Alex - I would use the full path name just to be clear about that
>manage.py file.
> 
>
>
>
>
>
>
>​[Alex] Good idea, thank you.
>​
> 
>
>
>
>Alex - in the mainstream YP documentation, the build directory is
>consistently referred to as "Build Directory."  When I use the term in a
>chapter or section I try to link the term to the formal definition in the
>dev-manual.  I don't link every occurrence
> but the first ones to appear in major sections or chapters.  The link is
>http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#build-
>directory 
><http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#build
>-directory>.  When I am referring to an actual Build Directory, I format
>it using a different font (Courier) and use the actual name.  So, if it
>is the default Build Directory, I say
> the build directory, and the word "build" appears in the font reserved
>for filenames and commands throughout the YP documentation.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>​[Alex] Let's change it then to "Build Directory", I think this conveys
>the proper message.​
>
> 
>
>
>
>
>>=============================================
>>
>>
>>When using the buildslist and builddelete commands, you need to consider
>>the following:
>>
>>
>>* For default configurations, your working directory must be the "build"
>>directory.  Using these command from the "build" directory allows Toaster
>>to find the "toaster.sqlite" file, which is located in the "build"
>>directory.
>>
>>
>>* For other database configurations, it is possible that you can use
>>these commands from a directory other than the "build" directory.  To do
>>so, the "toastermain/settings.py" file must be configured to point to the
>>correct database backend.
>>
>>
>>It is recommended to always call "manage.py" from the "build" directory.
>>
>>==========================================================
>>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

Re: Toaster documentation, 1.6 release

[Barros Pena, Belen]

I have added the "Setting up a Toaster Instance on a Remote Host" section
to the wiki:

https://wiki.yoctoproject.org/wiki/Toaster#Setting_up_a_Toaster_Instance_on
_a_Remote_Host

Please review the content. There are a couple of things in there I have
questions about:

* "Clone a separate, local Git repository of the Toaster master branch to
use for running the Web server." Does this refer to the 1.6 release or
master branches? 

* $ nohup bitbake --observer-only -u toasterui &

Is the above command complete?

Cheers

Belén


On 20/03/2014 09:54, "Barros Pena, Belen" <belen.barros.pena@intel.com>
wrote:

>Thanks, Scott!
>
>This needs to be reviewed by Alex and Paul: hopefully they can provide
>some feedback.
>
>Cheers
>
>Belén
>
>On 19/03/2014 19:15, "Scott Rifenbark" <srifenbark@gmail.com> wrote:
>
>>Belen, 
>>
>>Here is a version from me based purely on the text from the link in the
>>original email from Alex.  I culled out some stuff that seemed to be
>>"behind the scenes" information for future development and just
>>concentrated on what I saw as how this stuff needed
>> to be set up now.
>>
>>
>>One thing I am unclear of ....  It seems that the bigger picture here is
>>not simply setting up an instance of Toaster on a remote host.  But,
>>rather, setting up stuff so that you can log build information from
>>multiple instances of toaster that might be
>> spread around on various machines.  And, to do this you can set up a
>>common logging server and web server.  Is that right assumption?  That is
>>the assumption I based the front part of the section on.  If not, I need
>>more of the bigger picture.
>>
>>
>>
>>Give me some feedback on this and we will then take it to the next level.
>>
>>Thanks,
>>Scott
>>
>>
>>---------------------------------------
>>
>>
>>Setting up a Toaster Instance on a Remote Host
>>
>>
>>
>>
>>
>>Under normal circumstances, starting Toaster causes three things happen:
>>
>>
>>* A BitBake server starts
>>
>>* The Toaster UI starts, which connects to the BitBake server on one side
>>and to the SQL database on the other side
>>
>>* The web server starts, which reads the database and displays the web
>>user interface
>>
>>
>>Situations exist, however, where you might want to have multiple
>>instances of Toaster running on various remote machines.  You can create
>>this situation by basically modifying how toaster starts and where the
>>common SQL database resides.  You are able to do
>> this because it is not required that Toaster starts the above set of
>>components in order to run.  Minimally, an instance of Toaster requires
>>just one of the components to run.  Consequently, you are free to
>>manually start as many or few of the components as
>> you need rather than using the Toaster script to cause all three things
>>to happen.
>>
>>
>>The concepts for setting up multiple instances of Toaster revolve around
>>maintaining a common SQL database and Web server that show data from that
>>common database and then setting up separate instances of BitBake servers
>>and Toaster user interfaces for each
>> separate BitBake build directory.  Note that the common SQL database and
>>the Web server shows data from all the various BitBake builds.  Setting
>>the SQL database outside of any BitBake build directories maintains a
>>separation layer between the various builds.
>>
>>
>>The database is persistent because the logging database is set up
>>external to the database server (e.g. MySQL).  It is not even necessary
>>to run the BitBake servers, the SQL server, and the Web server on the
>>same machine.  Each component can be run on its own
>> machine.
>>
>>
>>Here are the steps to get set up:
>>
>>
>>1. Set up the SQL Logging Server and the Web Server
>>
>>
>>You can use any SQL server out of the box (e.g. apt-get install
>>mysgl-server for an Ubuntu system) works.  If you are concerned about
>>performance, you might want to hand-tune the server.  You must set up
>>proper username and password access for the server.
>> You need administration rights for the mysql root account.  Realize that
>>this is not the same thing as root access on the machine.
>>
>>
>>Clone a separate, local Git repository of the the Toaster master branch
>>to use for running the web server.  You do not perform builds on this
>>tree.  You need to create this local repository away from any build
>>areas.
>>
>>
>>In the separately cloned tree for the web server, edit the
>>bitbake/lib/toaster/toastermain/settings.py file so that the "DATABASES"
>>value points to the previously created database server.  Use the username
>>and password you established earlier.
>>
>>
>>Run the database sync scripts to create the needed tables as follows:
>>
>>
>>     python bitbake/lib/toaster/manage.py syncdb
>>
>>     python bitbake/lib/toaster/manage.py migrate orm
>>
>>
>>Start the web server using the following command:
>> 
>>
>>     python bitbake/lib/toaster/manage.py runserver
>>
>>
>>
>>2. Enable build logging to the common SQL server for each build directory
>>you are using.
>>
>>
>>Edit _build local_ bitbake/lib/toaster/toastermain/settings.py to alter
>>the "DATABASES" value to point to the common SQL logging server.
>>
>>
>>
>>Start the BitBake server using the following command:
>>
>>
>>     bitbake --postread conf/toaster.conf --server-only -t xmlrpc -B
>>localhost:0 && export BBSERVER=localhost:-1
>>
>>
>>Start the logging user interface using the following command:
>>
>>
>>     nohup bitbake --observer-only -u toasterui &
>>
>>
>>NOTE: No hard-coded ports are used as there is enough code to run
>>autodiscovery for ports to prevent collisions.
>>
>>
>>At this point, you are ready to run your builds using commands such as:
>>
>>
>>     bitbake core-image-minimal
>>
>>
>>When you are finished, you need to be to kill the BitBake server for that
>>particular build area:
>>
>>
>>     bitbake -m
>>
>>
>>
>>3. Verify that it all works.
>>
>>
>>You should examine the logs and be sure that the logging worked, that
>>data is persistent, and that data from multiple builds from different
>>areas was supported.
>>
>>
>>---------------------------------------
>>
>>
>>On Tue, Mar 18, 2014 at 10:47 AM, Barros Pena, Belen
>><belen.barros.pena@intel.com> wrote:
>>
>>Hi Scott,
>>
>>As I mentioned, we would like to document how to set up a Toaster
>>instance
>>in a remote host. Alex Damian sent an email to the mailing list
>>explaining
>>the process back in February. This is it:
>>
>>https://lists.yoctoproject.org/pipermail/toaster/2014-February/000464.htm
>>l
>>
>>We are thinking of documenting this in the wiki for the moment, with
>>maybe
>>a link to it from the existing Toaster section in the Development Manual.
>>
>>Just contact any of us, or the Toaster mailing list, if you have any
>>questions.
>>
>>Thanks for your help with this!
>>
>>Belén
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>-- 
>_______________________________________________
>toaster mailing list
>toaster@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/toaster

Re: Toaster documentation, 1.6 release

[Barros Pena, Belen]

Thanks, Scott!

This needs to be reviewed by Alex and Paul: hopefully they can provide
some feedback.

Cheers

Belén

On 19/03/2014 19:15, "Scott Rifenbark" <srifenbark@gmail.com> wrote:

>Belen, 
>
>Here is a version from me based purely on the text from the link in the
>original email from Alex.  I culled out some stuff that seemed to be
>"behind the scenes" information for future development and just
>concentrated on what I saw as how this stuff needed
> to be set up now.
>
>
>One thing I am unclear of ....  It seems that the bigger picture here is
>not simply setting up an instance of Toaster on a remote host.  But,
>rather, setting up stuff so that you can log build information from
>multiple instances of toaster that might be
> spread around on various machines.  And, to do this you can set up a
>common logging server and web server.  Is that right assumption?  That is
>the assumption I based the front part of the section on.  If not, I need
>more of the bigger picture.
>
>
>
>Give me some feedback on this and we will then take it to the next level.
>
>Thanks,
>Scott
>
>
>---------------------------------------
>
>
>Setting up a Toaster Instance on a Remote Host
>
>
>
>
>
>Under normal circumstances, starting Toaster causes three things happen:
>
>
>* A BitBake server starts
>
>* The Toaster UI starts, which connects to the BitBake server on one side
>and to the SQL database on the other side
>
>* The web server starts, which reads the database and displays the web
>user interface
>
>
>Situations exist, however, where you might want to have multiple
>instances of Toaster running on various remote machines.  You can create
>this situation by basically modifying how toaster starts and where the
>common SQL database resides.  You are able to do
> this because it is not required that Toaster starts the above set of
>components in order to run.  Minimally, an instance of Toaster requires
>just one of the components to run.  Consequently, you are free to
>manually start as many or few of the components as
> you need rather than using the Toaster script to cause all three things
>to happen.
>
>
>The concepts for setting up multiple instances of Toaster revolve around
>maintaining a common SQL database and Web server that show data from that
>common database and then setting up separate instances of BitBake servers
>and Toaster user interfaces for each
> separate BitBake build directory.  Note that the common SQL database and
>the Web server shows data from all the various BitBake builds.  Setting
>the SQL database outside of any BitBake build directories maintains a
>separation layer between the various builds.
>
>
>The database is persistent because the logging database is set up
>external to the database server (e.g. MySQL).  It is not even necessary
>to run the BitBake servers, the SQL server, and the Web server on the
>same machine.  Each component can be run on its own
> machine.
>
>
>Here are the steps to get set up:
>
>
>1. Set up the SQL Logging Server and the Web Server
>
>
>You can use any SQL server out of the box (e.g. apt-get install
>mysgl-server for an Ubuntu system) works.  If you are concerned about
>performance, you might want to hand-tune the server.  You must set up
>proper username and password access for the server.
> You need administration rights for the mysql root account.  Realize that
>this is not the same thing as root access on the machine.
>
>
>Clone a separate, local Git repository of the the Toaster master branch
>to use for running the web server.  You do not perform builds on this
>tree.  You need to create this local repository away from any build areas.
>
>
>In the separately cloned tree for the web server, edit the
>bitbake/lib/toaster/toastermain/settings.py file so that the "DATABASES"
>value points to the previously created database server.  Use the username
>and password you established earlier.
>
>
>Run the database sync scripts to create the needed tables as follows:
>
>
>     python bitbake/lib/toaster/manage.py syncdb
>
>     python bitbake/lib/toaster/manage.py migrate orm
>
>
>Start the web server using the following command:
> 
>
>     python bitbake/lib/toaster/manage.py runserver
>
>
>
>2. Enable build logging to the common SQL server for each build directory
>you are using.
>
>
>Edit _build local_ bitbake/lib/toaster/toastermain/settings.py to alter
>the "DATABASES" value to point to the common SQL logging server.
>
>
>
>Start the BitBake server using the following command:
>
>
>     bitbake --postread conf/toaster.conf --server-only -t xmlrpc -B
>localhost:0 && export BBSERVER=localhost:-1
>
>
>Start the logging user interface using the following command:
>
>
>     nohup bitbake --observer-only -u toasterui &
>
>
>NOTE: No hard-coded ports are used as there is enough code to run
>autodiscovery for ports to prevent collisions.
>
>
>At this point, you are ready to run your builds using commands such as:
>
>
>     bitbake core-image-minimal
>
>
>When you are finished, you need to be to kill the BitBake server for that
>particular build area:
>
>
>     bitbake -m
>
>
>
>3. Verify that it all works.
>
>
>You should examine the logs and be sure that the logging worked, that
>data is persistent, and that data from multiple builds from different
>areas was supported.
>
>
>---------------------------------------
>
>
>On Tue, Mar 18, 2014 at 10:47 AM, Barros Pena, Belen
><belen.barros.pena@intel.com> wrote:
>
>Hi Scott,
>
>As I mentioned, we would like to document how to set up a Toaster instance
>in a remote host. Alex Damian sent an email to the mailing list explaining
>the process back in February. This is it:
>
>https://lists.yoctoproject.org/pipermail/toaster/2014-February/000464.html
>
>We are thinking of documenting this in the wiki for the moment, with maybe
>a link to it from the existing Toaster section in the Development Manual.
>
>Just contact any of us, or the Toaster mailing list, if you have any
>questions.
>
>Thanks for your help with this!
>
>Belén
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

Re: Toaster documentation, 1.6 release

[Scott Rifenbark]

[-- Attachment #1: Type: text/plain, Size: 5772 bytes --]

Belen,

Here is a version from me based purely on the text from the link in the
original email from Alex.  I culled out some stuff that seemed to be
"behind the scenes" information for future development and just
concentrated on what I saw as how this stuff needed to be set up now.

One thing I am unclear of ....  It seems that the bigger picture here is
not simply setting up an instance of Toaster on a remote host.  But,
rather, setting up stuff so that you can log build information from
multiple instances of toaster that might be spread around on various
machines.  And, to do this you can set up a common logging server and web
server.  Is that right assumption?  That is the assumption I based the
front part of the section on.  If not, I need more of the bigger picture.

Give me some feedback on this and we will then take it to the next level.

Thanks,
Scott

---------------------------------------

Setting up a Toaster Instance on a Remote Host


Under normal circumstances, starting Toaster causes three things happen:

* A BitBake server starts
* The Toaster UI starts, which connects to the BitBake server on one side
and to the SQL database on the other side
* The web server starts, which reads the database and displays the web user
interface

Situations exist, however, where you might want to have multiple instances
of Toaster running on various remote machines.  You can create this
situation by basically modifying how toaster starts and where the common
SQL database resides.  You are able to do this because it is not required
that Toaster starts the above set of components in order to run.
Minimally, an instance of Toaster requires just one of the components to
run.  Consequently, you are free to manually start as many or few of the
components as you need rather than using the Toaster script to cause all
three things to happen.

The concepts for setting up multiple instances of Toaster revolve around
maintaining a common SQL database and Web server that show data from that
common database and then setting up separate instances of BitBake servers
and Toaster user interfaces for each separate BitBake build directory.
Note that the common SQL database and the Web server shows data from all
the various BitBake builds.  Setting the SQL database outside of any
BitBake build directories maintains a separation layer between the various
builds.

The database is persistent because the logging database is set up external
to the database server (e.g. MySQL).  It is not even necessary to run the
BitBake servers, the SQL server, and the Web server on the same machine.
Each component can be run on its own machine.

Here are the steps to get set up:

1. Set up the SQL Logging Server and the Web Server

You can use any SQL server out of the box (e.g. apt-get install
mysgl-server for an Ubuntu system) works.  If you are concerned about
performance, you might want to hand-tune the server.  You must set up
proper username and password access for the server.  You need
administration rights for the mysql root account.  Realize that this is not
the same thing as root access on the machine.

Clone a separate, local Git repository of the the Toaster master branch to
use for running the web server.  You do not perform builds on this tree.
You need to create this local repository away from any build areas.

In the separately cloned tree for the web server, edit the
bitbake/lib/toaster/toastermain/settings.py file so that the "DATABASES"
value points to the previously created database server.  Use the username
and password you established earlier.

Run the database sync scripts to create the needed tables as follows:

     python bitbake/lib/toaster/manage.py syncdb
     python bitbake/lib/toaster/manage.py migrate orm

Start the web server using the following command:

     python bitbake/lib/toaster/manage.py runserver


2. Enable build logging to the common SQL server for each build directory
you are using.

Edit _build local_ bitbake/lib/toaster/toastermain/settings.py to alter the
"DATABASES" value to point to the common SQL logging server.

Start the BitBake server using the following command:

     bitbake --postread conf/toaster.conf --server-only -t xmlrpc -B
localhost:0 && export BBSERVER=localhost:-1

Start the logging user interface using the following command:

     nohup bitbake --observer-only -u toasterui &

NOTE: No hard-coded ports are used as there is enough code to run
autodiscovery for ports to prevent collisions.

At this point, you are ready to run your builds using commands such as:

     bitbake core-image-minimal

When you are finished, you need to be to kill the BitBake server for that
particular build area:

     bitbake -m


3. Verify that it all works.

You should examine the logs and be sure that the logging worked, that data
is persistent, and that data from multiple builds from different areas was
supported.

---------------------------------------


On Tue, Mar 18, 2014 at 10:47 AM, Barros Pena, Belen <
belen.barros.pena@intel.com> wrote:

> Hi Scott,
>
> As I mentioned, we would like to document how to set up a Toaster instance
> in a remote host. Alex Damian sent an email to the mailing list explaining
> the process back in February. This is it:
>
> https://lists.yoctoproject.org/pipermail/toaster/2014-February/000464.html
>
> We are thinking of documenting this in the wiki for the moment, with maybe
> a link to it from the existing Toaster section in the Development Manual.
>
> Just contact any of us, or the Toaster mailing list, if you have any
> questions.
>
> Thanks for your help with this!
>
> Belén
>
>

[-- Attachment #2: Type: text/html, Size: 7223 bytes --]

Toaster documentation, 1.6 release

[Barros Pena, Belen]

Hi Scott,

As I mentioned, we would like to document how to set up a Toaster instance
in a remote host. Alex Damian sent an email to the mailing list explaining
the process back in February. This is it:

https://lists.yoctoproject.org/pipermail/toaster/2014-February/000464.html

We are thinking of documenting this in the wiki for the moment, with maybe
a link to it from the existing Toaster section in the Development Manual.

Just contact any of us, or the Toaster mailing list, if you have any
questions.

Thanks for your help with this!

Belén