From: Kyrre M Begnum <Kyrre.B<egnum@iu...> - 2004-04-23 07:52:08
Now that we have the possibility to build networks, let us take a glance
at the future and what other applications we need. I want to discuss one
particular aspect, namely the dynamic of the site. I want to have a
working demonstration of a expanding site for the paper on autonomous
I will stay at home today and make a programm called mln-server.pl. This
will be a prototype server that runs on a service host. I will also create
a client, called mln-client.pl (perhaps mln is inaprpriate here?) that
will be able to communticate with the mln-server. Virtual machines have
the client, and they use it to tell the server when and how they want to
be upgraded. This should not be too hard to program as long as I don't go
into the decision making process of how they want to change. The test,
case will be that they have another mln-file ready, and they'll send that.
## A little hop: A Transactional model for the dynamics of a virtual site.
The virtual site has a couple of actions that one has to make sure are
successfull: The morphing of a stemcell into a host, the upgrade of the
fabric. Lots of things can break along the way. How do keep track of the
changes being made and if they successfull? We can learn a bit from
transactional theory here, like databases. Before any action is taken,
a transaction is started, and when the action is done, a commit will end
that particular transaction. This will make sure that the same action is
not done twice. Appointed secretaries will have to monitor the transaction
list and identify what actions might have timed out.
So in the first run, there will be no negotiation process.
Kyrre M Begnum
Rom 1.755 7.etg