Re: edge.validation.linaro.org
> > One thing that worries me is KVMs lack of (can anyone correct me if I'm > wrong) USB pass-through support. This means we may have a hard time reaching > USB serial adapters or USB-to-device links in general. For that reason my > testing will use headless virtualbox instances. > usb pass through should not be a problem for kvm. I've never tried it personally but it looks doable [1]. Worst case scenario, we could always expose the usb serial consoles over the network using a tool like we did for the demo in budapest, but I don't think it would be necessary. -Paul Larson [1] http://libvirt.org/formatdomain.html#elementsUSB ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: edge.validation.linaro.org
W dniu 31.08.2011 16:39, Paul Larson pisze:
On Wed, Aug 31, 2011 at 6:57 AM, Zygmunt Krynicki<
zygmunt.kryni...@linaro.org> wrote:
Edge is just a point on the roadmap. If staging is fast enough to
scrap/deploy then we may just use staging all the time.
I was actually thinking it might be nice to have staging as more of a fluid
concept using VMs. We could set up a semi-permanent staging VM that gets
updated with trunk of everything every {day, week, whatever}, but also have
other VMs available for upgrade testing, and testing individual changes.
That way, for instance, if you need to test a dispatcher change that
affects a certain type of board you don't have at home, you can simply wait
for one of those boards to become available in the lab, mark it offline,
bring up a vm and do some testing with it. Likewise, it could be used to
setup and test an invasive change to the dashboard. All that would be
required is a few static port mappings on the firewall, and a server capable
of handling a few KVM sessions (which I'd like to look at getting soon for
this purpose and others).
I agree with usefulness of staging as a fast-to-production model While
using VMs is a possibility it does not really preclude me from
experimenting with this design.
For safety reasons a VM might be needed once we start to run stuff as
root. Currently all edge stuff is owned by a normal user and runs as the
web server.
One thing that worries me is KVMs lack of (can anyone correct me if I'm
wrong) USB pass-through support. This means we may have a hard time
reaching USB serial adapters or USB-to-device links in general. For that
reason my testing will use headless virtualbox instances.
I have created lp:~zkrynicki/+junk/edge where this stuff is being created.
Thanks
ZK
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: edge.validation.linaro.org
On Wed, Aug 31, 2011 at 6:57 AM, Zygmunt Krynicki <
zygmunt.kryni...@linaro.org> wrote:
> Edge is just a point on the roadmap. If staging is fast enough to
> scrap/deploy then we may just use staging all the time.
>
I was actually thinking it might be nice to have staging as more of a fluid
concept using VMs. We could set up a semi-permanent staging VM that gets
updated with trunk of everything every {day, week, whatever}, but also have
other VMs available for upgrade testing, and testing individual changes.
That way, for instance, if you need to test a dispatcher change that
affects a certain type of board you don't have at home, you can simply wait
for one of those boards to become available in the lab, mark it offline,
bring up a vm and do some testing with it. Likewise, it could be used to
setup and test an invasive change to the dashboard. All that would be
required is a few static port mappings on the firewall, and a server capable
of handling a few KVM sessions (which I'd like to look at getting soon for
this purpose and others).
Thanks,
Paul Larson
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: edge.validation.linaro.org
W dniu 31.08.2011 13:35, Alexander Sack pisze: I wonder, once we have staging.v.l.o, do we really need edge anymore? Perhaps not. We will see once we have both. What problems does edge protect us from that we really care about? Maybe we can avoid running 3 instead of two instances and have 3 instead of 2 code rollout stages? What do you mean by "rollout stages"? my understanding is that with staging and edge you have three rollout steps/stages: 1. daily trunk That's what staging is about 2. edge testing That's how we can evaluate non-invasive production changes instantly (faster than staging). 3. production That's what we released last month (although there are some voices that we may want to put more recent software there too). i wondered about what risks the "edge" stage protects us from and if we can avoid that step as it comes with additional overhead on maintenance, process and time-to-production. Edge is just a point on the roadmap. If staging is fast enough to scrap/deploy then we may just use staging all the time. I guess I'm trying to say "stay tuned". Thanks ZK ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: edge.validation.linaro.org
On Wed, Aug 31, 2011 at 1:12 PM, Zygmunt Krynicki < zygmunt.kryni...@linaro.org> wrote: > W dniu 31.08.2011 01:30, Alexander Sack pisze: > >> On Tue, Aug 30, 2011 at 6:55 PM, Zygmunt Krynicki< >> zygmunt.kryni...@linaro.org> wrote: >> >> Hi there. >>> >>> The validation team has a new edge website, >>> http://edge.validation.linaro. >>> **org/<http://edge.validation.**linaro.org/<http://edge.validation.linaro.org/>> >>> that reflects the development >>> >>> trunk of all of our components. This site can be used to check latest >>> development effort, test bug fixes and, to some degree, use new features. >>> >>> This website mimics the concept of now-defunct edge.launchpad.net. That >>> is, it allows for new code to run on top of the production database. >>> >>> This has important ramifications: >>> >>> 1) Unsafe code could cause data loss >>> 2) New features that depend on database schema modifications cannot be >>> tested this way. >>> 3) Non-website features such as dispatcher and part of the scheduler >>> cannot >>> be tested this way. >>> >>> For addressing those we will soon deploy staging.validation.linaro.**orgthat >>> works on a periodic snapshot of the production database. >>> >>> >>> I will be posting an update with instructions on how to replicate this >>> setup if necessary and details about the periodic automatic roll >>> out/upgrade >>> procedure. >>> >>> >>> Thanks for the heads up. >> >> I wonder, once we have staging.v.l.o, do we really need edge anymore? >> > > Perhaps not. We will see once we have both. > > > What problems does edge protect us from that we really care about? Maybe >> we >> can avoid running 3 instead of two instances and have 3 instead of 2 code >> rollout stages? >> > > What do you mean by "rollout stages"? > > my understanding is that with staging and edge you have three rollout steps/stages: 1. daily trunk 2. edge testing 3. production i wondered about what risks the "edge" stage protects us from and if we can avoid that step as it comes with additional overhead on maintenance, process and time-to-production. -- - Alexander ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: edge.validation.linaro.org
W dniu 31.08.2011 01:30, Alexander Sack pisze: On Tue, Aug 30, 2011 at 6:55 PM, Zygmunt Krynicki< zygmunt.kryni...@linaro.org> wrote: Hi there. The validation team has a new edge website, http://edge.validation.linaro. **org/<http://edge.validation.linaro.org/> that reflects the development trunk of all of our components. This site can be used to check latest development effort, test bug fixes and, to some degree, use new features. This website mimics the concept of now-defunct edge.launchpad.net. That is, it allows for new code to run on top of the production database. This has important ramifications: 1) Unsafe code could cause data loss 2) New features that depend on database schema modifications cannot be tested this way. 3) Non-website features such as dispatcher and part of the scheduler cannot be tested this way. For addressing those we will soon deploy staging.validation.linaro.orgthat works on a periodic snapshot of the production database. I will be posting an update with instructions on how to replicate this setup if necessary and details about the periodic automatic roll out/upgrade procedure. Thanks for the heads up. I wonder, once we have staging.v.l.o, do we really need edge anymore? Perhaps not. We will see once we have both. What problems does edge protect us from that we really care about? Maybe we can avoid running 3 instead of two instances and have 3 instead of 2 code rollout stages? What do you mean by "rollout stages"? Thanks ZK ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: edge.validation.linaro.org
On Tue, Aug 30, 2011 at 6:55 PM, Zygmunt Krynicki < zygmunt.kryni...@linaro.org> wrote: > Hi there. > > The validation team has a new edge website, http://edge.validation.linaro. > **org/ <http://edge.validation.linaro.org/> that reflects the development > trunk of all of our components. This site can be used to check latest > development effort, test bug fixes and, to some degree, use new features. > > This website mimics the concept of now-defunct edge.launchpad.net. That > is, it allows for new code to run on top of the production database. > > This has important ramifications: > > 1) Unsafe code could cause data loss > 2) New features that depend on database schema modifications cannot be > tested this way. > 3) Non-website features such as dispatcher and part of the scheduler cannot > be tested this way. > > For addressing those we will soon deploy staging.validation.linaro.orgthat > works on a periodic snapshot of the production database. > > I will be posting an update with instructions on how to replicate this > setup if necessary and details about the periodic automatic roll out/upgrade > procedure. > > Thanks for the heads up. I wonder, once we have staging.v.l.o, do we really need edge anymore? What problems does edge protect us from that we really care about? Maybe we can avoid running 3 instead of two instances and have 3 instead of 2 code rollout stages? -- - Alexander ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
edge.validation.linaro.org
Hi there. The validation team has a new edge website, http://edge.validation.linaro.org/ that reflects the development trunk of all of our components. This site can be used to check latest development effort, test bug fixes and, to some degree, use new features. This website mimics the concept of now-defunct edge.launchpad.net. That is, it allows for new code to run on top of the production database. This has important ramifications: 1) Unsafe code could cause data loss 2) New features that depend on database schema modifications cannot be tested this way. 3) Non-website features such as dispatcher and part of the scheduler cannot be tested this way. For addressing those we will soon deploy staging.validation.linaro.org that works on a periodic snapshot of the production database. I will be posting an update with instructions on how to replicate this setup if necessary and details about the periodic automatic roll out/upgrade procedure. Thanks Zygmunt Krynicki ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
