Payload Canister delivered to Launch Pad…

The STS-120 payload canister is being delivered to the launch pad
Yesterday, the Payload canister has been delivered to the launch pad. What can be seen is the “protective cover” of the canister. It is now being stored at the pad. After Discovery has been moved over to the pad (starting on Saturday evening), the payload will be integrated into it (at least this is what I think will happen – remember, I am still learning…).

I’ve also heard that the weather forecast looks good for the rollout. Processing flow in the VAB still seems to be great, so the rollout as scheduled is very likely. However, this seems not to bring in extra contingency, as some work usually done in the VAB seems to have moved over to the pad. The reason was weather, where the favorable weather on Saturday shall be used. In any case, the NASA guys are doing an excellent job.

So far, everything still looks like an October, 23rd launch is still quite probable.

on ommysql packaging

I thought I share an interesting conversation that went over the rsyslog mailing list. Even though it buried in the mailing list archive, I think here is a better place to be displayed. Feedback is much appreciated.


> —–Original Message—–
> From: Michael Biebl
> Sent: Friday, September 28, 2007 10:23 AM
> To: rsyslog-users; Rainer Gerhards
> Subject: Re: [rsyslog] rsyslog 1.19.8 released
>
> 2007/9/27, Rainer Gerhards :
> > repeat message processing. The MySQL functionality is now taken out
> of
> > the core package, but its tarball is still contained in the main
> tarball
> > (so it is still a single download for everything). This is part of
> the
> > effort to fully support third-party plugins. Rsyslog 1.19.8 is a
>
>
> To be honest, I don’t particularly like this change. It increases the
> work for package maintainers (like me). You now have to maintain two
> source packages. Having a non-standard tarball inside a tarball
> doesn’t help there. It even worsens things, as stuff like “make dist”
> or “make distcheck” doesn’t work anymore for a cvs checkout.
> There’s also the problem of which version of the plugins will be
> compatible with the core version (upgrade scenarios, keeping them in
> sync, etc.)
> It also adds complexity for the developer (as he has to maintain an
> additonal set of build files).
> As you were talking about 3rd party plugins (with the emphasis on 3rd
> party) I don’t understand the benefit of splitting out the mysql
> plugin as it is you who develops the mysql plugin, not a third party.
> Do you actually intend to create a separate tarball for each plugin in
> the future?
>
> What was wrong with the –enable-mysql configure switch? I don’t see
> any benefits, only disadvantages. You know, if it ain’t broken, why
> fix it ;-)
>
> Cheers,
> Michael

Hi Michael,

as I have blogged, I am not yet sure about how to handle the situation. I am also consulting with Autotools experts, any advise is appreciated.

Two packages seem useful, especially when more plugins become available (I myself think about email and a couple of other databases). Many folks also do not like the idea of having to have libmysql present on the system just to install rsyslog – with a core package and the plugin, those can only install the core (and that will probably the majority of cases).

What I have not yet found – and I have very limited expertise in this area – is how to do that in the best possible way.

Oh, and some more background: ones the plugin interace has matured (I expect this in 3 to 6 month), I intend to actually use ommysql with its own version number. Versioning will be handled by the interface (that part is already present, but no code for it yet as there is only a release 1 of it). So, in the medium to long term, ommysql *will* be a separate project – maybe one with a different maintainer, as I am no mysql guy.

Does this make sense? As I said, comments are much appreciated…

Rainer

It was not a MLP…

Look at the red circle and you will see it can't be a MLP
In my last posting I thought I had spotted a mobile launcher platform. But I was wrong. As a friend pointed out, it can not be. Look at the red circle – this is a table. It would be a real gigantic table, if it were a MLP. So it can’t be…

changed the blog url

Yesterday, I talked with some of my friends about the blog. They said: “hey, cool, but what do you do after 2010?”. I was stunned. But, yes there are right. In 2010, the space shuttle is retired. Some years later (hopefully sooner than later), the Ares rockets will launch cargo and humans into space, to the Moon, hopefully to Mars and at some distant time even beyond that.

When I started this blog, the main intension was to provide a trip report from my launch viewing. But it is also interesting to write about all the cool things that go together with launch preparations. So I may continue to drop a post or two on future missions. And, of course, I will try to view an Ares launch when it is time to do so (though I guess tickets to the first human flight will be very hard to get hold off).

Writing about Ares under shuttlelaunch.gerhards.net? No, that sounds strange. So I have changed the blog url to spacelaunch.gerhards.net, just to be prepared for the new things to come. And, hey, you never know if some friendly folks will sponsor me a trip to see an Ariane or Russian launch… ;)

I have set up a redirector to redirect traffic with the old urls to the new ones. In the first day, that may not work very well (due to technical issues, for the geeks: DNS propagation delay). I’d also appreciate if you could update your bookmarks. Sorry for any hassle this url change causes – but I think it has a good reason…

Is this a mobile launcher platform?

Is this a mobile launcher platform (MLP)?
I found this picture on one of the NASA webcams. I wonder if it is a mobile launcher platform (MLP)? If so, is it the one to be used for Discovery? I do not know enough about VAB processing flow, but it might be that the full stack (orbiter, boosters, external tank) be assembled first. When this is done, they might be lowered to the mobile launcher platform. If that’s the case, then my speculation will probably be right. If anybody knows for sure, please drop me a comment. And, of course, I’ll also try to find out…

work log for 2007-09-26

work log for rsyslog:

2007-09-26
– applied patch provided by varmojfekoj to support building ommysql
in its own way (now also resides in a plugin subdirectory)
– fixed a bug in cvthname() that lead to message loss if part
of the source hostname would have been dropped

One Day of Contingency Recovered?

Shuttle rolls out of VAB to the launch pad (STS-83 mission)
As I have read on the web, Discovery seems to have one more contingency day left in its launch schedule. The wizards in the VAB seem to have done real magic. Originally, the rollout to the pad was scheduled for Sunday. Now, it seems to be Saturday, September 29th at 8pm ED. Well, that’s maybe half a day of contingency if I think more about it. Extra contingency time is very desirable, because four days were lost when a damage on a landing gear strut was found and needed to be repaired. Even though the repair was ultra-fast, almost all remaining contingency time was used up. Now, with the excellent processing flow, NASA keeps again up with it. My hope is that some other activities will also be earlier than planned, leaving even more contingency. As we all know, spaceflight is inherently complex and there is a good chance that extra contingency (spare) time is needed at some stage.

For those interested: I assume that NASA TV carries some video footage from the VAB rollout.

Its very promising to see work progressing so well. To me, it looks more and more like the first launch attempt is indeed on the October, 23rd. Let’s hope for the best, including good weather. I’ll keep you updated.

News Source: http://www.raumfahrer.net/forum/cgi-bin/YaBB.pl?num=1173608035/480 (german!)
Picture: VAB rollout during the STS-83 mission (this is NOT STS-120!), Photo Credit: NASA

oops … did not notice comments…

Sorry to all folks who commented on my blog – I did not react at all. Shame over me. If you take time to provide your ideas, you deserve at least a little bit of reaction.

The problem is that I am an email junkie – I set mail notifications for everything I do. And if I don’t get an email notification, it is almost sure that I forget about it. And when setting up the blog, I forgot to enable email notifications. Guess what happened then…

The good new is that the notifications are now enabled, so I will now reply much more promptly. I enjoy your thoughts and discussions, so keep them coming. Maybe we can even manage to network a couple of folks who want to view this launch. Wouldn’t that be nice? So, if you are in for it – please spread word about my little blog and help get more cool people to read, comment and discuss :)

hotels, hotels, hotels…

A typical view of Titusville hotel reservation before launch day - unavailable ;)
Did I mention that I had quite some trouble booking hotel rooms for my shuttle launch? The nights in Orlando were no problem at all – Orlando simply has so many hotels of all kinds, it is really hard to book them out… But Titusville and Cocoa Beach is a different story.

I made the mistake to not immediately book hotel rooms after I booked my launch transportation tickets from KSC. When I was ready to do that, my fellow “launch viewers” already had taken the majority of rooms. Interestingly, the 22nd was most heavily booked – but the 23rd was much easier to get. It looks like a lot of folks believe in a total on-time launch – or hope to be able to extend if the launch is delayed. The later, I think, is a false impression.

I finally managed to book rooms, but I have to change hotels every now and then. The interesting fact about this is that on certain days I need to pack all my luggage into the car – and if that is on a launch day, I’ll need to drive with my fully-packed car up to KSC. I am not sure what the security guards will say about this… For now, I hope it will not really be necessary, but, if so, I hope I can get along with it. Of course, once I am down there in the Titusville area, I’ll check with the hotels if I can put my luggage into some room even when I have checked out.

So I was all set. Ahem – was I? Actually, I made a second mistake: I was so sure that Orlando hotels are no problem that I simply forgot to book a room over there! Boing… Crazy me. What now? Well, book ASAP. And that I did. Thankfully, I was able to book at the Residence Inn, what was exactly what I wanted. But the bad news was that pricing had changed. I suspect there is higher demand for rooms due to the shuttle launch. Whatever it was, it costs me around 20 bucks (plus tax, of course), per day. Bottom line: if you want to visit a shuttle launch and still stay in Orlando, book as early as possible even if it typically is no problem to get a nice room in the Orlando area…

Did not manage to release 1.19.8 today…

Sorry folks, I didn’t manage to release 1.19.8 today. There was simply too much other activity that required attention. So I couldn’t finally decide on how to distribute from now on. Anyhow, it is my firm intention to release 1.19.8 tomorrow.

The good news, though, is that some folks are already testing that code. Maybe I get some feedback until tomorrow morning – and maybe that even helps me to get a better release…