Networking: Good news
Chris Malton
As per my comments on IRC earlier, I had a call from iSolutions earlier.
They are more than happy to agree to us using their internet connection,
with seemingly next to no issues. The few questions I was posed, I have
either answered to them, or posed below:
I now need to find a spare wall port in 25/1009 - Can somebody go and
try and find a port that also has a 13A power socket in close
proximity? If we are having a helpdesk, in a bay like last year, please
can we try and put HD in a bay that has power/net so we can keep our
stuff under Blueshirt eyes.
Also, I need a responsible member of staff/somebody who's allowed to
register DHCP leases. I don't care who is it, but I need somebody.
Don't all shout at once! I'm envisaging either Rob, or Jeremy being
involved here. Please comment!
So, if people can respond to me, and let me know who's going to be
responsible, and if somebody can locate a wall port for me that would be
much appreciated. I need all of this agreed for November 28th please,
so that iSolutions can make the needed firewall and networking changes
to permit us to use that port.
I should add that with the amount of logging I have planned, I was
advised it was possibly "too much logging, and you might want to scale
it back a bit".
Thank in advance.
Regards,
Chris M
Rob Spanton
Chris Malton wrote:
> Also, I need a responsible member of staff/somebody who's allowed to
> register DHCP leases. I don't care who is it, but I need somebody.
> Don't all shout at once! I'm envisaging either Rob, or Jeremy being
> involved here. Please comment!
There's a general problem with the "competition networking" right now.
Its development is not being performed in an open manner. This
definitely needs to change to avoid things going wrong, reduce bus
factors etc.
We'll only pursue this if the code and designs for the networking are
online, and the discussion about them is on-list.
Cheers,
Rob
Chris Malton
> There's a general problem with the "competition networking" right now.
> Its development is not being performed in an open manner. This
> definitely needs to change to avoid things going wrong, reduce bus
> factors etc.
>
Last time I tried to get git repos on Optimus for this, they were
politely refused by jmorse, telling me to sort it out it somewhere else
first
As such, I've started hosting them on my own server. I refer you to the
projects with names beginning sr-network at [0]. There's four of them -
all with what should be useful descriptions.
I would also like to point out that, much as I'd like to have everyone's
input on everything with the network, and much as I'd like to
incorporate everything, we simply can't do everything, and in fact, we
should keep it as simple as possible. I'd also like to point out that
last time I started a discussion, it petered out with no clear
resolution anyway.
I would also like to point out that the documentation I have written so
far, as far as I'm concerned, should not be made public. This is due to
the fact that it contains standard passwords, architecture drawings etc,
which if we were running a corporate network - which as I see it, we
essentially are - would never be public knowledge. They would on;y be
available to people who build the infrastructure.
We have 3 weeks to get something working and up and running for Tech Day
1. I've put a hell of a lot of work into it so far, and as far as I'm
concerned, I'd rather have something that works in 3 weeks time, rather
than still be bickering about the little details and not have anything
that works.
If you, or anyone else, for that matter wants to take the project off my
hands, and get something working before Tech Day 1, they are more than
welcome.
Chris
Rob Spanton
> Last time I tried to get git repos on Optimus for this, they were
> politely refused by jmorse, telling me to sort it out it somewhere else
> first
I expect he meant your public_git.
> As such, I've started hosting them on my own server. I refer you to the
> projects with names beginning sr-network at [0]. There's four of them -
> all with what should be useful descriptions.
Ok, great. (First I've heard of these)
> I would also like to point out that, much as I'd like to have everyone's
> input on everything with the network, and much as I'd like to
> incorporate everything, we simply can't do everything, and in fact, we
> should keep it as simple as possible.
Keeping things simple and working with other people are not orthogonal
things.
> I would also like to point out that the documentation I have written so
> far, as far as I'm concerned, should not be made public. This is due to
> the fact that it contains standard passwords, architecture drawings etc,
> which if we were running a corporate network - which as I see it, we
> essentially are - would never be public knowledge. They would on;y be
> available to people who build the infrastructure.
Then remove the passwords...
Cheers,
Rob
Rob Spanton
On Wed, 2011-11-09 at 19:53 +0000, Chris Malton wrote:
> As such, I've started hosting them on my own server. I refer you to
> the projects with names beginning sr-network at [0]. There's four of
> them - all with what should be useful descriptions.
I can't see any URLs that I can feed to git on your site. What should I
prepend the git repo's name with?
Cheers,
R
Rob Spanton
> last time I started a discussion, it petered out with no clear
> resolution anyway.
What things were left without conclusion?
R
Rob Spanton
On Wed, 2011-11-09 at 19:53 +0000, Chris Malton wrote:
> I would also like to point out that the documentation I have written so
> far, as far as I'm concerned, should not be made public. This is due to
> the fact that it contains standard passwords, architecture drawings etc,
> which if we were running a corporate network - which as I see it, we
> essentially are - would never be public knowledge. They would on;y be
> available to people who build the infrastructure.
I'll follow up on this point slightly more as well. (I was busy in a
doing the other day when this came up.)
We are not building a "corporate network". We are building a network
for a community-run robotics competition. Keeping things secret (beyond
passwords) harms both the community as well as the project about which
things are being kept secret.
Cheers,
Rob
Peter Law
>> I would also like to point out that the documentation I have written so
>> far, as far as I'm concerned, should not be made public. This is due to
>> the fact that it contains standard passwords, architecture drawings etc,
>> which if we were running a corporate network - which as I see it, we
>> essentially are - would never be public knowledge. They would on;y be
>> available to people who build the infrastructure.
Rob wrote:
> We are not building a "corporate network". We are building a network
> for a community-run robotics competition. Keeping things secret (beyond
> passwords) harms both the community as well as the project about which
> things are being kept secret.
I concur - this isn't a corporate network, though it may be of that
scale. As rob says, we're building a community thing, in which context
having things open is generally the way to improve them <insert
open-source methodology>.
Peter
Chris Malton
> Hey Chris,
>
> On Wed, 2011-11-09 at 19:53 +0000, Chris Malton wrote:
>> As such, I've started hosting them on my own server. I refer you to
>> the projects with names beginning sr-network at [0]. There's four of
>> them - all with what should be useful descriptions.
> I can't see any URLs that I can feed to git on your site. What should I
> prepend the git repo's name with?
>
Replace <projectname> with the name of the project as displayed at the
gitweb home page.
I don't, as it stands, offer anonymous git read-only.
Chris
Chris Malton
> You can clone from http://git.cmalton.me.uk/<projectname>
>
> Replace <projectname> with the name of the project as displayed at the
> gitweb home page.
I should add that I've since pushed more stuff to the various SR network
repos on my server, and will be doing so again shortly.
Following on from the fact that nearly all of the documentation is now
on the Wiki [0], I would like to make two requests again:
- Please could a member of staff at Southampton (be that Rob, Jeremy, or
somebody else) discuss with me about being the person responsible for
the IP address(es).
- Please could somebody, and this can be anyone with access to B25, go
into B25, into room 1009, and locate the most suitable network port for
me to plug into, and get its faceplate number. I need a single port
number, that's it. It'll take somebody 5 minutes. I am not coming to
Soton the Sunday before just to get a port number! I believe the ports
are under the desks.
Thanks in advance,
Chris