Webconverger PXE boot

[Esben]

I'm running Webconverger version 14 via PXE using
"fetch=http://x.x.x.x/filesystem.squashfs" as a boot option.

The newer versions of Webconverger do not include a squashfs image. How
does PXE booting work now that Webconverger uses git?

[Kai Hendry]

Hi there Esben,

Related bug: https://github.com/Webconverger/webc/issues/103

PXE boot is not supported. If anyone wants to try get it working
again, they are welcome to. I don't see the need.

My experiences with netbooting haven't been great. I like to think
since that Webconverger is so easy to install onto any old hard disk
or another USB key, PXE booting is not really relevant.

You might find the contributed http://webconverger.org/pxeboot/ guide helpful.

Kind regards,

[Joshua Cowles]

The relevance is in central management of upgrades and settings.  I suppose at this point it may be simpler to run FOG and netboot from that and download a new image as necessary, but I have also been interested in PXE booting and would be willing to help, to the extent that I can, if some people are interested in tackling it.

--
You received this message because you are subscribed to the Google Groups "Webconverger Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to webc-users+...@googlegroups.com.
To post to this group, send email to webc-...@googlegroups.com.
Visit this group at http://groups.google.com/group/webc-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

--
Josh Cowles

Fond du Lac Public Library

920-929-7080 x3956 (On-Site)

techs...@fdlpl.org (IT Requests)

[Kai Hendry]

On 22 April 2013 16:37, Joshua Cowles <cow...@fdlpl.org> wrote:
> The relevance is in central management of upgrades and settings. I suppose
> at this point it may be simpler to run FOG and netboot from that and
> download a new image as necessary, but I have also been interested in PXE
> booting and would be willing to help, to the extent that I can, if some
> people are interested in tackling it.

Webconverger offers "central management of upgrades and settings" as a
subscriber feature http://webconverger.com/pricing

We have a settings control panel and an upgrade API
http://webconverger.org/upgrade/

And of course this works in many more cases where PXE is simply not
available, or you can't afford to setup the appropriate architecture /
server.


Of course, if you don't want to use our commercial services you are
welcome to hack on getting a netboot working again. I'm happy to host
the work. I might even test it. ;)


Kind regards,

[Phillip Smith]

On 23 April 2013 01:37, Joshua Cowles <cow...@fdlpl.org> wrote:

The relevance is in central management of upgrades and settings.  I suppose at this point it may be simpler to run FOG and netboot from that and download a new image as necessary, but I have also been interested in PXE booting and would be willing to help, to the extent that I can, if some people are interested in tackling it.

This is my usage model for an internal application in a manufacturing environment. On an isolated network with no internet connectivity, the subscriber option is not a viable one. I'm stuck on 14 as well, but having said that it's running well and I don't really NEED to update to the latest. Stability is more important here.

[Kai Hendry]

Hi there Phillip,

On 23 April 2013 00:42, Phillip Smith <fuk...@gmail.com> wrote:
> This is my usage model for an internal application in a manufacturing
> environment. On an isolated network with no internet connectivity, the
> subscriber option is not a viable one. I'm stuck on 14 as well, but having
> said that it's running well and I don't really NEED to update to the latest.
> Stability is more important here.

Well you have the option to add your API options to a build upon
http://webconverger.org/develop/

OR

use http://custom.webconverger.com/ commercial offering, where your
config would be preloaded. Useful for folks who aren't on the
Internet. This might be a requirement for payment processing.


I like to think https://github.com/Webconverger/webc/commits/master is
stable as it can possibly be. It's pretty rare a Web application is
broken through an update. However if it is, I think its in everyone's
best interest to fix it and document it openly and slowly improve the
status quo. Btw with the http://webconverger.org/upgrade API, you
could do fancy things like binary search for issues.

Kind regards,

[Kai Hendry]

On 4 November 2013 23:17, Waldemar <schl...@gmail.com> wrote:
> We are also stuck on v14 because of this change when moving from the
> well-established squashfs to gitfs. Hopefully this is something that can be
> resolved.

We are not moving back to squashfs. We are committed to gitfs since it
solves the upgrade problem elegantly.
http://webconverger.org/upgrade

That said, I would like to get a PXE boot solution working, it's just
that I don't have time to work on it.

Kind regards,